API Request Errors
Routific uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error based on the information provided in the request (for example a required parameter missing from the request). Codes in the 5xx range indicate an error with Routific's servers, these tend to be rare creatures — do let us know if you found one!
429 - Rate Limit
We here at Routific employ a rate limit across all our endpoints. Our rate limits are generous enough that we don't expect anyone to hit them. But, in case if you hit the limit we do return a 429 response along with a message in the body indicating when the limit would be reset. If you do find yourself consistently hitting the the limit due to increase in order volume or business growth, please reach out to us at [email protected] to explore options.
Some 4xx errors can be handled programmatically based on the error type and message returned in the body of the response.
| HTTP Status Code | Description |
|---|---|
| 200 - OK | Everything worked as expected. |
| 400 - Bad Request | The request validation failed, most likely due to a missing mandatory parameter |
| 401 - Unauthorized | API key is either invalid or missing from the request |
| 403 - Forbidden | API key doesn't have the required permissions to perform the request |
| 404 - Not Found | Requested endpoint or resource doesn't exist |
| 429 - Too Many Request | Exceeded the number of API calls that can be made within an interval. Please retry the request after the limit has been reset |
| 50X - Server Errors | Something went wrong inside Routific's servers |
Webhook Event Delivery and Retries
When Routific fires an event, we send the payload to your endpoint and expect a 2xx HTTP response to confirm receipt.
Retries
If your endpoint does not respond with 2xx, Routific will retry the delivery automatically with exponential backoff.
Auto-disable on repeated failure
If your endpoint continues to fail after repeated attempts, Routific will automatically deactivate your webhook to prevent further failed deliveries. When this happens:
- Your webhook status changes to Inactive in the Webhooks settings page.
- All Admin users in your organization receive an email notification.
- No further events are delivered until you re-enable the webhook.
To re-enable, fix the issue at your end, then toggle the webhook back to Active in Company Settings -> Routific webhook
Use a Queue
For production integrations, we recommend having your webhook endpoint immediately acknowledge receipt with a 200 OK and then process the payload asynchronously. This keeps your endpoint fast, prevents timeouts, and avoids failures caused by slow downstream processing.