Errors
This section provides information about the error handling mechanisms and error responses returned by the Dedit API. Understanding the possible errors that can occur and their corresponding error codes and messages is essential for effective integration with the API.
The Dedit API follows standard HTTP status codes to indicate the success or failure of a request. In case of an error, the API returns an appropriate HTTP status code along with an error response body containing additional details about the error.
Some commonly encountered error codes include:
400
Bad Request -- The request could not be understood by the server due to malformed syntax.
401
Unauthorized -- Your API key or JWT is invalid.
403
Forbidden -- The resource requested is hidden for administrators only.
404
Not Found -- The specified resource could not be found.
405
Method Not Allowed -- You tried to access a resource with an invalid method.
406
Not Acceptable -- You requested a format that isn't JSON.
410
Gone -- The resource requested has been removed from our servers.
418
I'm a teapot.
429
Too Many Requests -- You're requesting too many resources! Slow down or continue being increasingly throttled.
500
Internal Server Error -- We had a problem with our server. Try again later.
503
Service Unavailable -- We're temporarily offline for maintenance. Please try again later.
Last updated