Skip to main content
The Metabind API uses standard HTTP status codes and returns detailed error objects to help you understand and handle errors effectively.

Error Response Format

Error responses from API endpoints follow a consistent format:
A request to a route that does not exist returns 404 with the body {"error": "Not Found"}.

HTTP Status Codes

Success Codes

Client Error Codes

Server Error Codes

Common Error Codes

Validation Errors

Resource Not Found

Duplicate Resource

Invalid Status Transition

Component In Use

Circular Dependency

Rate Limiting

When you exceed the rate limit, you’ll receive a 429 Too Many Requests response:
The retryAfterSeconds field indicates the number of seconds to wait before retrying. Data tool execution, and requests rejected while the service is busy, return RATE_LIMIT_EXCEEDED instead.

Rate Limit Headers

Most 429 responses include this header:

Handling Errors

JavaScript Example

Retry Strategy

For transient errors (5xx, 429), implement exponential backoff:

Best Practices

Use the code field for programmatic error handling, not the message field which may change.
The details object contains valuable debugging information. Log it for troubleshooting.
Implement exponential backoff and respect the Retry-After header.
Validate data client-side before making API calls to avoid unnecessary 400 errors.