Authorizations
B2B’s White Label API uses OAuth2. Currently there is only one supported authentication flow:
- clientCredentials allows you to access your own B2B account (First-Party Integration) and performs transactions against the public API. This oauth2 flow is well suited for this API, as it allows machine-to-machine communication.
Every call to the API has to be authenticated with an OAuth2 Token. In order to request this token, you will need to have sandbox or production API Keys (client id and client secret) that will be needed to generate a credential in order to negotiate an ephemeral access token.
Every request must be accompianed by an Authorization
header with a value that follows the following schema: Bearer ACCESS_TOKEN
Path Parameters
Body
Response
Successful response
If the transaction represents a BUY, SELL or SWAP operation, this object will detail the trade operation information.
UUID used as trade identifier.
UUID used as Transaction identifier. Useful to relate this object trade with a transaction object.
UUID used as quote identifier.
Arbitrary string used as end_user identifier.
Indicates the exchange rate used for conversion.
Indicates trade's applied fee.
Indicates the amount of units or equivalence in the quote for base currency.
Indicates the amount of units or equivalence in the quote for quote currency.
Indicates the base currency involved in the quotation.
Indicates the quote currency involved in the quotation.
ISO DateTime indicating creation date of trade.