Integration Flow:
- Fetch available assets (fiat, crypto, and payment methods).
- Use those to fetch real-time quotes. Include the destination wallet when requesting a Binance BUY quote.
- Create a transaction using the selected provider. Binance BUY transactions require the destination wallet again at this step.
- Redirect users to the checkout URL.
- Handle transaction updates through webhooks or via long polling our transaction endpoints.
Authenticate API requests with your partner API key in the
X-ORKI-API-KEY header.Base URLs
All endpoints in this guide use the
/api/v1/partner base path. Use the same paths with the base URL for your intended environment.
Use TEST API keys with the sandbox base URL. The sandbox supports the partner endpoints documented in this guide, including Transak staging quotes, checkout-session creation, and sandbox transaction retrieval. Creating a sandbox transaction does not initiate payment. Provider completion, status callbacks, and webhook delivery are not simulated end to end.
API request logs
Authenticated requests to/api/v1/partner endpoints are recorded in the API Logs view in the Terminal after the API key and accountโs Partner API access have been validated.
Each entry contains the request path, HTTP method, response status code, success or failure state, and timestamp. Request parameters, request bodies, response bodies, and API key values are not included in these log entries.
Logs are environment-specific: sandbox requests appear only in the sandbox account data, while production requests appear only in production. API logging does not change an endpointโs request or response structure.
Destination wallets for BUY transactions
Orki does not configure a partner-level destination wallet for ramp purchases. The destination wallet and network are determined separately for each transaction.- For most providers, the buyer enters or confirms the destination wallet and network during the providerโs hosted or embedded checkout.
- You may supply
wallet_addresswith quote and transaction requests. Providers that support a prefilled wallet receive it as part of their checkout configuration. - For Binance BUY transactions,
wallet_addressis required during both quote discovery and transaction creation. Without it, the Binance quote is marked unsupported and cannot be selected. - The selected ramp provider sends the purchased crypto directly to the transactionโs specified or confirmed wallet. Orki does not custody or redirect it.
1. Get Supported Crypto Currencies
Endpoint:GET /api/v1/partner/crypto-currencies
Description: Returns a list of all supported cryptocurrencies and their networks.
Response Example:
2. Get Supported Fiat Currencies
Endpoint:GET /api/v1/partner/fiat-currencies
Description: Lists our supported fiat currencies for transactions.
Response Example:
3. Get Payment Methods
Endpoint:GET /api/v1/partner/payment-methods
Description: Returns all supported payment methods for buying or selling crypto.
Required Query Parameters:
Response Example:
4. Get Quotes
Endpoint:GET /api/v1/partner/quotes
Description: Fetches exchange rate quotes from all supported providers.
Required Query Parameters:
Optional Query Parameters:
Example Request:
5. Create Transaction
Endpoint:POST /api/v1/partner/transactions
Description: Creates a new transaction and returns a checkout URL for the user to complete payment.
JSON Body:
Example Request:
6. Handle Webhooks
Description: Receive updates for transaction status changes. Sample Payload:transaction.successtransaction.failed
โ When to Use
- You want full control of UX and transaction logic.
- Youโre integrating crypto buy/sell within your product flow.
- You need flexibility in pricing, routing, or KYC handling.
๐ Next Steps
- Obtain your API key from the Partner Dashboard.
- Review the OpenAPI Reference for detailed request/response models.
- Set up Webhooks to monitor transaction lifecycle.