Error Handling
Arrotech Hub uses standard HTTP response codes to indicate the success or failure of an API request.
HTTP Status Codes
| Code | Meaning | Description |
|---|---|---|
200 | OK | The request was successful. |
201 | Created | Successfully created a resource (e.g., a new Workflow). |
400 | Bad Request | The request was unacceptable, often due to missing a required parameter. |
401 | Unauthorized | No valid API key provided. |
403 | Forbidden | The API key doesn't have permissions to perform the request. |
404 | Not Found | The requested resource doesn't exist. |
422 | Validation Error | Request payload failed validation check. |
429 | Too Many Requests | You have hit your rate limit. |
500, 502, 503, 504 | Server Error | Something went wrong on Arrotech's side. |
Error Response Format
When an error occurs, the response body will contain details:
{
"detail": [
{
"loc": ["body", "workflow_id"],
"msg": "field required",
"type": "value_error.missing"
}
]
}
Rate Limits
Usage is limited to ensure stability for all customers.
- Free Tier: 100 requests per minute.
- Developer Tier: 1,000 requests per minute.
- Scale/Enterprise: Custom limits.
[!tip] If you receive a
429error, check theRetry-Afterheader to see how long to wait before trying again.