Response Codes

API Response Codes

Complete reference of HTTP status codes returned by the SignQuick API.

Status Codes Reference

200 OK

Request succeeded. Response body contains the requested data. Used for GET requests and successful updates.

201 Created

Resource created successfully. Response includes the new resource with its ID. Used for POST requests.

400 Bad Request

Invalid request parameters or body. Check the error message for specific validation failures.

401 Unauthorized

Missing or invalid API key. Ensure your Authorization header contains a valid Bearer token.

403 Forbidden

Valid credentials but insufficient permissions. Check your plan limits or resource ownership.

404 Not Found

Resource not found. Verify the ID exists and you have access to it.

429 Too Many Requests

Rate limit exceeded. Check Retry-After header for wait time. See our rate limits documentation.

500 Internal Server Error

Server-side error. Retry with exponential backoff. If persistent, contact support with the request ID.

Error Handling Tips

Implement exponential backoff for 429 and 500 errors (start at 1s, max 30s)

Parse the error.message field from JSON responses for human-readable descriptions

Log request IDs from response headers for debugging and support requests

Check X-RateLimit-Remaining header to proactively avoid 429 errors

See Full Error Reference

Detailed error codes with examples and resolution steps.

Error Reference