# BackOffice API

### General Information

TraderEvolution Back-Office REST API allows to build integrations with CRMs, Core broker/bank systems, and corporate websites to exchange information and automate processes. The API is organized around REST. It has predictable resource-oriented URLs, accepts request bodies, returns JSON-encoded responses, and uses standard verbs from <mark style="color:red;">`HTTP/1.1`</mark> as well as responds in JSON (<mark style="color:red;">`application/json`</mark>) format with standard HTTP error codes.

Please note that this portal describes in detail only the most commonly used methods and flows, while the whole API has much wider possibilities!&#x20;

{% hint style="warning" %}
You can try the Swagger which includes all methods of this API at <https://sandbox.traderevolution.com:8443/proftrading/rest/swagger-ui.html#>
{% endhint %}

All API calls are grouped into sections corresponding to system entities, you can find them structured as a tree in the left part of the page. Each section contains a set of endpoints for interacting with a particular object. It is supplied with a brief manual to facilitate understanding and help manage the API. You can find examples of API requests and responses in the documentation.

### Error Codes and Messages <a href="#error-codes-and-messages" id="error-codes-and-messages"></a>

`200 OK`  this return code is used for successful requests.

`204 No content` return code is used when there is no content.

`400 Bad request` return code is used for *bad requests*.

`401 Unauthorized` return code is used when the user is *unauthorized*.&#x20;

`404 Not found` return code is used when the requested entity is *not available*.

`405 Method not allowed` return code is used when the *method is not allowed*.

`406 Not acceptable` return code is used for *unacceptable* values.

`500 Internal server error` return code is used for *internal server errors*. <br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guide.traderevolution.com/traderevolution-api/traderevolution-apis/backoffice-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.