Webhook Setup
Receive real-time notifications for order status changes, messages, and deliveries directly to your server.
How Webhooks Work
Server-to-Server Communication
Instead of constantly polling our API to check if your service order is completed or if an admin replied to your chat, you can provide us with a Webhook URL. Whenever an important event occurs, we will send an instantaneous HTTP POST request containing a JSON payload to your URL.
5-Second Timeout
Your server must respond with a 2xx status code within 5000ms, otherwise the request is marked as failed and dropped.
Secure Delivery Data
Credentials are never sent directly in the webhook payload. You must fetch the API when an order completes to retrieve sensitive data.
Event Payloads
All webhooks are sent as POST requests with Content-Type: application/json. Your endpoint should inspect the event key to determine how to process the payload.
Event: order_chat_message
Fired when an admin or customer sends a message or file attachment into the order's chat thread.
Event: order_status_changed
Fired when an admin updates the status of your service order to PROCESSING or COMPLETED.
Event: order_delivered
Fired when an admin executes a delivery. You should immediately make a GET /v1/order/:id request to retrieve the newly generated credentials in the deliveryData field.
Event: order_reopened
Fired when a completed order is reopened under warranty via your API request.
Example Receiver (Express.js)
Here is a basic example of how you can configure a Node.js Express server to listen for our webhooks and process the events optimally.