API Calls

In general, calls will be made in the following sequence:

All the specific endpoints will be found in your Sandbox.

🚧
POST calls
All the API calls (including Get Token API) use POST.
If you use GET, you will receive a 404 error.

AUTHORIZING API CALLS

Your API calls need to be authorized using an OAuth2 token.
This token is generated using the Client ID and Secret Key found in your Sandbox.
The token will be valid for 30 minutes.
Make sure to include the token in the Authorization header of the API calls in the Bearer format e.g. "Bearer < token >".

Instructions on how to send the Get Token API can be found here.

Bringg will return "401 Unauthorized" errors if there is an issue with the authentication of the API call. e.g. if the token has expired or the wrong secret key/token was used
Bringg will return "403 Forbidden" errors if there is an issue with the payload itself e.g. if the incorrect task_id is specified.

All secure connections to Bringg require Transport Layer Security (TLS) 1.2 or later.

For SSL connections, the following ciphers suites are supported: