Error handling

Find out how Filemail API notifies about errors.

When the API returns HTTP code greater or equal to 400 then the request must be treated as failed. Here are a few typical HTTP status codes you might expect:

• 400 Bad request - your request was incorrectly formatted, the content type was incorrect, some parameters were missing, the parameters provided were not correct.

• 401 Unauthorized - missing or incorrect api key or logintoken.

• 404 Not found - misspelled endpoint name.

• 409 Conflict - the operation could not be performed due to invalid state of your account or transfer. This code also covers cases related to infected files, blocked content and storage limits reached.

• 429 Too many requests - rate limit or daily quota exceeded.

• 500 Internal server error - an unexpected server error occurred. This usually means you'll need to contact support so we can investigate the problem.

When you encounter any of the error codes be ready to parse the response to figure out the error details and act upon it. Here is the schema for a typical error response and a validation error (error responses usually include an array of validation errors under validationerrors field):