Skip to main content
The Fanfare API uses conventional HTTP response codes to indicate the success or failure of an API request.

Error Response Format

All error responses follow a consistent JSON structure:

HTTP Status Codes

Success Codes (2xx)

Client Error Codes (4xx)

Server Error Codes (5xx)

Common Error Types

Authentication Errors

Missing Authentication
Invalid Token
Secret Key Required

Validation Errors

Field Validation Failed
Missing Required Field
Database Constraint Violation

Resource Errors

Resource Not Found
Resource Conflict

State Errors

Queue Not Open
Queue Full
Auction Closed

OTP Errors

OTP Expired
Invalid OTP

Session Integrity Errors

Some endpoints may require additional session integrity checks before a consumer can continue:

Rate Limiting Errors

Order Limit Errors

When a consumer exceeds purchase limits:

Error Handling Best Practices

1. Check HTTP Status Code First

2. Respect Retry-After Headers

3. Display User-Friendly Messages

Map error codes to user-friendly messages:

4. Log Errors for Debugging

Include relevant context in error logs:

Error Recovery Strategies

Transient Errors (5xx)

Implement exponential backoff:

Token Expiration

Automatically refresh tokens when expired: