Skip to main content
GET
Auth method: Signed (HMAC) — this endpoint requires the full set of signed headers: x-access-id, x-request-id, x-timestamp, and an HMAC-SHA256 authorization signature. See Authentication.
All conversion endpoints share a bucket of 10 requests per minute per merchant, on top of the general limit. See Rate limits. The quote is an estimate at current prices. The final figures are fixed when you create the conversion.

Headers

string
required
Base64-encoded HMAC-SHA256 signature of {"timeStamp":"<x-timestamp>","requestId":"<x-request-id>","accessId":"<x-access-id>"}, signed with your access secret. The request body is not part of the signature.Example: "pV3n0o8kq0lK2mJ8bZ1yq3Yt6hR0cXK9u4mVJ2l9sE0="
string
required
ISO 8601 timestamp; must be within 5 minutes of server timeExample: "2026-10-15T09:45:53.000Z"
string
required
A unique UUID v4 per requestExample: "550e8400-e29b-41d4-a716-446655440000"
string
required
Your API access ID provided by TenderExample: "your-access-id-here"

Path parameters

string
required
Source chain IDExample: "ethereum"
string
required
Source coin ID (for example usdt, not the symbol USDT)Example: "usdt"
string
required
Amount to convert, in the source coin. Must be greater than zero.Example: "100"

Query parameters

string
Destination chain ID for a crypto swap. Use fiat to quote a fiat conversion.Example: "solana"
string
Destination coin ID for a crypto swap, or a fiat currency ID (for example ngn) when toChain is fiat. If omitted, the destination is the source coin.Example: "sol"

Response

string
required
success on successExample: "success"
string
required
Human-readable result messageExample: "success"
object
required
Conversion quote

Errors

All return HTTP 400.

Authorizations

authorization
string
header
required

Signed (HMAC) authentication. Required headers: x-access-id, x-request-id (UUID v4), x-timestamp (ISO 8601, must be within 5 minutes of server time), and authorization: the Base64 HMAC-SHA256 of the JSON string {"timeStamp":"","requestId":"","accessId":""} (keys in that order, no whitespace) using your access secret. The request body, method and path are not signed. The API key must be linked to an outlet.

Headers

authorization
string
required

Base64-encoded HMAC-SHA256 signature of {"timeStamp":"<x-timestamp>","requestId":"<x-request-id>","accessId":"<x-access-id>"}, signed with your access secret. The request body is not part of the signature.

x-timestamp
string<date-time>
required

ISO 8601 timestamp; must be within 5 minutes of server time

x-request-id
string<uuid>
required

A unique UUID v4 per request

x-access-id
string
required

Path Parameters

chain
string
required

Source chain ID

coin
string
required

Source coin ID

amount
string
required

Amount in the source coin; must be greater than zero

Query Parameters

toChain
string

Destination chain ID, or fiat

toCoin
string

Destination coin ID, or fiat currency ID when toChain is fiat

Response

Quote

status
string
required
Example:

"success"

message
string
required
Example:

"success"

data
object
required