BackOffice API

TraderEvolution Back-Office management REST API 1.1

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 HTTP/1.1 as well as responds in JSON (application/json) 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!

You can try the Swagger which includes all methods of this API at https://sandbox.traderevolution.com:8443/proftrading/rest/swagger-ui.html#

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

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.

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.