Base URL
Authentication
All API requests must include your API key in theapi-key header:
An API key authenticates your account — it does not restrict which operations can be performed. There is no read-only API key: any valid key can create a checkout or accept a conversion. Treat every key as full-access and scope access at your own layer.
X-API-Version header with the current build tag.
Request format
EveryPOST endpoint rejects unknown fields. A typo’d or extra key in the request body returns 400 rather than being silently ignored — so a request that used to work will not start behaving differently after a field is renamed.
Query parameters behave the opposite way: an unrecognised parameter on a GET is ignored, and an unparseable value for a known parameter is generally dropped rather than rejected. See the individual endpoint pages for the specifics.
Status codes
Error responses
Error body format is not uniform, so branch on the HTTP status rather than on the body. Three shapes exist:-
A JSON object, correctly typed — the conversion endpoints:
On a refusal,
POST /v2/rfq/acceptinstead returns its full response object, carryingstateandreason. -
A JSON object sent with
Content-Type: text/plain—POST /v2/crossramp_checkout. The body is still JSON despite the header, so parse the body and ignore the content type. -
No body at all — the single-record and list
GETroutes write only the status line on401,404, and500.

