Overview
Last updated
Was this helpful?
Last updated
Was this helpful?
Learn more about the different endpoints of Swap API:
- Get information about a blockchain network supported by clipper.
- Generate potential asset swap quotes. Obtain pricing and essential details for informed decision-making
- Facilitates blockchain transaction preparation and security by returning the required signature and data. Use it for efficient and secure asset swaps
In order to prevent abuse on the API we implement rate limits on the requests, to overcome these limits as an aggregator get in contact with the support team to get API credentials (user and password) .
These credentials will be used to authorize every request made in the following endpoints: /rfq/pool
, /rfq/quote
and /rfq/sign
The API uses the Basic authentication method. You have to include the credentials (username:password
) in the headers in base64
format.
Example: If your password is username is clipper
and your password is clipperdocs
the base64 of clipper:clipperdocs
is Y2xpcHBlcjpjbGlwcGVyZG9jcw==
Authorization
→ Basic Y2xpcHBlcjpjbGlwcGVyZG9jcw==
400
Bad Request - Invalid data in the request
401
Unauthorized
403
Forbidden Error
500
Internal Server Error
503
External Service Error
error_code
and data
are not always present
Examples
These codes appear in the field errorCode
422
Invalid input data
409
Quote problems
If we make a request to endpoint and the body does not have the field chain_id
(required param), the API response will look like similar to this:
If we make a request to endpoint and we send an input_asset_symbol
that clipper does not support, the API response will look like similar to this
If we make a request to endpoint and we send invalid credentials