Errors

DJfindr uses standard HTTP response codes to indicate the success or failure of API requests.

How the codes are generally categorized:

• 2xx codes: Indicate a successful operation.

• 4xx codes: Indicate a client error, often due to incorrect or missing information in the request (e.g., missing a required parameter or invalid data).

• 5xx codes: Indicate a server-side issue with DJfindr's systems (these are uncommon).

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	The 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 were sent in a short period. Implement exponential backoff for retries.
500, 502, 503, 504	Server Errors	Internal server errors. These indicate an issue with DJfindr's servers (rare occurrences).