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
Response
OK
Indicates limit type.
BUY
, SELL
Indicates the currency in which the limit has been expressed.
ARS
, USD
Indicates the period in which the limit applies.
DAILY
, MONTHLY
, YEARLY
Indicates the maximum frequency allowed per period for a given operation type and currency.
Indicates the maximum tradable amount allowed per period for a given operation type and currency.
Indicates the spent frequency related to the allowed_frequency declared. It must comply with the following invariant: allowed_frequency >= consumed_frequency
.
Indicates the spent tradable amount related to the allowed_frequency declared. It must comply with the following invariant: allowed_amount >= consumed_amount
.