OxaPay Swap API

Overview

The OxaPay Swap API provides programmatic access to supported pairs, rates, calculations, swap requests, and swap history using a General API Key. Applications should not treat a prior quote as a guaranteed future result unless the endpoint explicitly provides that commitment. They should store request identifiers, separate calculation from execution, handle ambiguous timeouts without blind resubmission, and reconcile completed swaps with account balances and history. The OxaPay Swap API owner should publish stable error semantics and guidance on whether correction, retry, status lookup, or escalation is appropriate.

For example, OxaPay Swap API works by accepting a documented swap request and returning trackable state; important risks include unsupported assets, stale quotations, duplicate requests, execution failure, and unreconciled delivery. These operations use the General API Key documented for swap access. Integrations should validate asset symbols, amount precision, minimums, and returned status, while protecting the General API Key. For OxaPay Swap API, the application should preserve a correlation path from request construction through response, asynchronous completion, and final business state.

For OxaPay Swap API, assertions should verify final provider and business state, not only an HTTP status or locally mocked response. OxaPay’s swap service includes endpoints for discovering swappable assets and minimums, checking real-time rates, calculating expected output, executing a swap request, and reviewing history. Supported pairs, minimums, fees, and execution results can change. A displayed rate or calculated amount is an estimate tied to current market and service conditions. A successful transport result from OxaPay Swap API should not be interpreted beyond the exact API state documented by the provider.