The Notifications endpoints allow clients to retrieve a history of notifications generated by the platform (such as transaction status changes) and to manually trigger resending of notifications if needed.
GET /notification/orderRetrieves previously sent system notifications related to deposit, withdrawal, or trade orders.
Authentication: Requires Bearer Token.
π Link to full response example in the documentation
GET /notification/order/:orderId/resendTriggers the resend of a notification for a specific order.
Required parameter:
orderId: ID of the deposit, withdrawal or trade order.
Authentication: Requires Bearer Token.
π Link to full usage example in the documentation
Notifications are tied to specific orders and represent system events like status changes.
Useful when a webhook is missed or a manual resend is needed.
Can be integrated into internal monitoring or recovery workflows.
1. What types of orders support notifications?
Notifications are generated for deposit, withdrawal, and trade orders.
2. How do I know if the resend was successful?
The API will respond with
200 OKand a message confirming the resend.
3. Can I list all past notifications?
Yes. The listing endpoint retrieves all past notifications based on access permissions.
4. Is authentication required for these endpoints?
Yes. Both endpoints require a valid Bearer Token.
Now you're ready to work with Notifications in the Bloquo API. For more information, visit the official documentation.