Quotes & rates
Get an indicative rate
Price a corridor before a recipient exists.
Path parameters
orgIdstringRequiredThe opaque organization id issued to you, normally CUID-shaped (for example
cmsx…). It is not anorg_-prefixed alias. Pass it unchanged in every organization-scoped path.
Query parameters
fromstringRequiredThree-letter ISO 4217 source currency code.
tostringRequiredThree-letter ISO 4217 destination currency code.
amountstringOptionalDecimal string. Omitting it prices $100 rather than returning an amountless rate, so a UI that renders the response shows a figure the user never typed. Pass the amount you are actually showing.
Behavior
What the recipient receives, the fee, the rate, and the corridor's minimum and maximum, with nothing created yet. This is what you show while someone is still choosing an amount.
Indicative, not locked. The binding price comes from
POST /quotes/offramp against a real recipient. Show this as an
estimate and confirm the final number before sending.
The fee is deducted from the amount you send, so
destinationAmount = (sourceAmount - fee) x rate.
The query parameters are not validated on the server today. Always
send from, to and a decimal amount as described: a missing
currency can answer 500 INTERNAL rather than a 400, and a
non-numeric amount returns amounts that are not numbers.
Responses
200Indicative price
Body · PreviewQuote
indicativebooleanOptionalAlways true here. This is an estimate, not a locked rate.
sourceAmountobjectOptionalAlways a decimal string, never a float and never base units. Floats lose cents at scale; base units mean every integrator re-derives the exponent.
Show 2 properties
currencystringRequiredamountstringRequired
destinationAmountobjectOptionalAlways a decimal string, never a float and never base units. Floats lose cents at scale; base units mean every integrator re-derives the exponent.
Show 2 properties
currencystringRequiredamountstringRequired
feeobjectOptionalCharged on the send side and deducted before conversion.
Show 2 properties
currencystringRequiredamountstringRequired
totalDebitobjectOptionalWhat leaves your balance. On
GET /ratesthe fee is deducted from the send rather than added on top, so this equalssourceAmount. A payout link's preview adds the fee on top, so there it issourceAmount + fee. Read this field rather than assuming either.Show 2 properties
currencystringRequiredamountstringRequired
ratestringOptionalThe indicative mid-rate, before the fee: destination units per source unit converted, "1 USD = 17.01 MXN".
destinationAmount = (sourceAmount - fee) x rate. This is a different number fromPayout.rate, which is the effective rate with the fee inside (destination over source), so it reads lower by the fee share for the same conversion. The rate did not move.limitsobjectOptionalThe corridor's floor and ceiling, in the source currency.
Show 2 properties
minstringOptionalmaxstringOptional
Errors
400BAD_REQUEST: no such corridor for this organization.INDICATIVE_PRICING_UNAVAILABLE: your routing publishes no indicative rates. Do not retry; checkcapabilities.indicativePricingon the corridors call and price against a real recipient withPOST /quotes/offrampinstead.401The key was refused. Nothing ran.
UNAUTHORIZED: missing, invalid or revoked, or a key on a route that does not accept one.KEY_EXPIRED: the key passed the expiry it was issued with. Issue a new one; an expired key cannot be rotated.KEY_IP_NOT_ALLOWED: the key is pinned to source addresses and this request came from another.
403A valid key that may not make this call. Nothing ran.
FORBIDDEN: the key belongs to a different organization.ACCOUNT_BLOCKED: API access for your organization is suspended, and every key is refused until we lift it. Contact support.
429Too many requests. The default ceiling is 100 requests per minute per API credential on a 60-second window. High-volume payout and reconciliation routes declare a 600/minute override, and batch submission a 30/minute ceiling. A separate 2,000/minute per-source-IP abuse ceiling always applies.
Obey
Retry-After; it is in seconds and is authoritative. A 429 means the request was refused before the handler ran. Retry reads normally; retry an idempotent mutation with its sameIdempotency-Key.
Error body · Error
typestringRequiredStable machine-readable code.
detailstringRequiredWhat went wrong, in a sentence. Always a string, so
detail.toLowerCase()is safe.More
This is the field to read on
BAD_REQUESTandPROVIDER_REJECTED, where the type alone does not name the condition.messagestringRequiredThe same text as
detail, kept for integrations written beforedetailexisted. Readdetail.resolutionstringOptionalWhat to do about it, when there is a specific answer. It is not on every error (it is absent on
BAD_REQUEST,NOT_FOUND,PAYOUT_NOT_CANCELABLEandDESTINATION_ACCOUNT_NOT_FOUND), so treat it as optional and fall back todetail.statusintegerRequiredHTTP status, repeated in the body.
statusCodeintegerRequiredThe same value as
status, kept for integrations written beforestatusexisted. Readstatus.requestIdstringRequiredQuote this to support and we can find the exact request. Also sent as the
x-request-idresponse header, which is the only place it appears on a successful response. Success bodies do not carry it. Send your ownx-request-idon the request and we use it, so your trace and ours share one identifier; otherwise we mint one.errorsarray of stringOptionalPresent on VALIDATION_ERROR; names each field that failed.
originalIdempotencyKeystringOptionalOn
DUPLICATE_REQUEST_DETECTEDonly. Send the request again with this to receive the original payout instead of making a second one. Without it there is no way to recover except by risking a double payment.originalPayoutIdstringOptionalOn
DUPLICATE_REQUEST_DETECTEDonly. The payout the first request created.originalBatchIdstringOptionalOn a batch
DUPLICATE_REQUEST_DETECTED. The run the first request created.originalRequestIdstringOptionalOn a
409 PAYOUT_OUTCOME_UNKNOWNreplay. TherequestIdof the call whose outcome is unknown; quote it to support.existingRecipientIdstringOptionalOn
BANK_ACCOUNT_ALREADY_LINKED. The recipient in your organization that already holds this account.existingMethodIdstringOptionalOn
BANK_ACCOUNT_ALREADY_LINKED. The payment method on that recipient.
Branch on type, never on the status or the message. Every error type is listed with what to do about it.
Was this page helpful?