Introduction
Admin Gateway
On this page
- Introduction
Authentication
What made this section unhelpful for you?
On this page
- Authentication
gRPC
On this page
- gRPC
Errors
We use standard HTTP response codes to state the success or failure of API requests. It means that codes in the range
- 2xx indicate success and usually have response bodies,
- 4xx indicate errors with detailed answers to why a particular request failed,
- 5xx indicate errors on our servers.
What made this section unhelpful for you?
Status Codes
200
The request was performed successfully. You should receive a response with a body. 200 response bodies are listed in each endpoint's response section.
204
The request was performed successfully. You should receive a response without a body.
400
Invalid request, usually due to missing some required parameter.
401
Authorization information is missing or invalid.
403
Your API token does not have permission to perform the requested operation.
405
Wrong HTTP method used, eg. POST instead of GET
422
The server understands the content type of the request entity, and the syntax is correct, but it was unable to process the request.
500
Something went wrong on our end. You can contact our Product Support to check it.
What made this section unhelpful for you?
gRPC Error Handling
What made this section unhelpful for you?
On this page
- gRPC Error Handling
Examples
What made this section unhelpful for you?
On this page
- Examples
Branches, Offers, Roles
On this page
- Branches, Offers, Roles
Accounts
On this page
- Accounts
Payments
On this page
- Payments
Trading
On this page
- Trading
Prop Trading
On this page
- Prop Trading
Social Trading
On this page
- Social Trading
CRM Events
On this page
- CRM Events
FAQ
What made this section unhelpful for you?
On this page
- FAQ