Skip to main content
​
APIQuotesTerminal
Partner API logging and NGN quote availability

​
API request logs

  • Restored request logging for authenticated /api/v1/partner endpoints. Requests that pass API key and partner-access checks now appear in the account’s API Logs view in the Terminal.
  • API logs record the request path, HTTP method, response status code, success or failure state, and timestamp. Request and response bodies are not stored in these logs.
  • Sandbox and production logs are isolated. A request made through sandbox.money.orki.io does not appear in the production environment’s logs, and vice versa.
  • This is an observability update only; partner endpoint request and response structures have not changed.

​
NGN card quotes

  • Corrected BUY quote validation for Nigerian naira amounts. Valid NGN to BTC on mainnet quote requests using credit_debit_card can now return MoonPay when it is available for the requested amount and route.
  • Provider availability, exchange rates, and transaction limits remain dynamic and are confirmed during quote discovery.
​
APISandboxDocumentation
Sandbox base URL and API reference corrections

​
Environments and paths

  • Added the sandbox API base URL: https://sandbox.money.orki.io. Production remains available at https://api.money.orki.io.
  • Standardized partner API documentation on the /api/v1/partner base path in both environments.

​
API reference

  • Corrected the create-transaction and payment-method response examples.
  • Removed inactive partner quote-selection and separate SELL quote references. Both BUY and SELL quote discovery use GET /api/v1/partner/quotes with the type query parameter.
​
APIWebhooksProvidersDocumentation
Partner integration reliability and documentation updates

​
Partner API

  • Standardized authentication guidance and examples on the X-ORKI-API-KEY header. The partner API does not use the Authorization: Bearer scheme.

​
Quotes and providers

  • Clarified that Orki does not configure a partner-level destination wallet for ramp purchases. The destination is set per transaction and the selected provider delivers the purchased crypto directly to it.
  • Binance BUY quotes require wallet_address. When it is omitted, Binance is returned as unsupported and cannot be selected for transaction creation. The address is also required when creating the Binance BUY transaction. This does not change SELL quotes or BUY quotes from other providers.

​
Webhooks

  • Added partner_context to the webhook data reference. Client-owned API and widget transactions return the supplied value as data.partner_context, or null when it was omitted.
  • Aligned webhook event metadata with the documented transaction.success and transaction.failed names. Successful payloads use data.status: "success".