Error handling is a crucial part of any reliable and user-friendly Open API application. Unless you catch and process various errors, your users may experience 'janky' UI or may be prevented from performing certain essential actions entirely.
Broadly speaking, different error handling processes may be implemented depending on the layer where an error occurs.
- At the data/domain layer. In some cases, the cTrader backend may send the
ProtoErrorResmessage as a response to one of your requests. For operations related to orders, deals, or positions, you may also receive the
- At the domain/application layer. Users may perform actions that you have not accounted for in your code, resulting in your application behaving unexpectedly.
The mechanisms for handling errors at these levels are different and are described below.
Error Handling at the Data/Domain Layer¶
You may receive
ProtoOAOrderErrorEvent in the following situations (note that the list is not exhaustive).
- Attempting to place an order for a symbol for which the market is closed.
- Sending an incorrect or an unsupported message.
- Attempting to modify an order that is being executed.
- Sending a message after losing your connection to the cTrader backend.
ProtoErrorRes and the
ProtoOAOrderErrorEvent have the
description fields that contain precise information about the type of error that has occurred and its description. You can see the full list of all supported error codes in the
To make sure that your application does not 'break' in such cases, you can usually subscribe to callbacks that trigger when you receive an error response. The exact logic of these callbacks as well as how you can subscribe to them depend on the client you are using to establish a connection and listen to the messages stream.
Working With JSON
When operating with JSON, you can still reuse code from this tutorial; however, you would need to slightly modify it depending on your approach to serialisation/deserialisation and your preferred TCP/WebSocket client.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
When using the
twisted library to handle asynchronous operations, you have to subscribe to an error callback every time you send a new message as shown in the below example for
1 2 3 4 5 6 7 8
Error Handling at the Domain/Application Layer¶
The way you handle errors at the domain and application layers depends on your chosen programming language, UI framework, and the use cases you implement, making it difficult to provide specific code snippets and solutions.
However, the following recommendations can prove useful regardless of how you choose to integrated with the cTrader Open API.
- Always implemented a dedicated error state for major UI elements. This would prevent your application from 'breaking' entirely and allow for running in a semi-degradated state.
- Implement a secure and reliable logging mechanism that would record errors in a suitable location (e.g., local storage). If repeated errors occur, logging should simplify identifying and addressing their cause.
- Create a mechanism for users to inform you of errors. This can be as simple as providing your contact info within the application or as complicated as adding an automatic feedback submission service that triggers on new errors.
- Ensure that any resources used when errors occur are properly cleaned up. While most languages offer 'garbage collector' services, you may want to specify custom resource disposal logics.