Errors

HTTP response codes returned by the DJfindr API.

The DJfindr API uses standard HTTP response codes to indicate the outcome of a request.

• 2xx — Successful operation
• 4xx — Client error, often due to incorrect or missing information in the request
• 5xx — Server-side issue with DJfindr’s systems (uncommon)

Response codes

Code	Name	Description
200	OK	The request was successful and everything worked as expected.
400	Bad Request	The request was invalid, often due to missing or incorrect parameters.
401	Unauthorized	Authentication failed — no valid API key was provided.
402	Request Failed	Parameters were valid but the request could not be completed (e.g., a time slot was unavailable).
403	Forbidden	The API key does not have the necessary permissions to perform the requested operation.
404	Not Found	The requested resource could not be located.
409	Conflict	The request conflicts with another request (e.g., duplicate use of an idempotent key).
429	Too Many Requests	Too many requests in a short period. Implement exponential backoff for retries.
500, 502, 503, 504	Server Errors	Internal server errors indicating an issue with DJfindr’s servers (rare).