HTTP Response Codes and Errors
HTTP Status Codes
The FAA API attempts to return a meaningful HTTP status code for every request, including requests that resulted in an error.
- Success. The system returned an expected response.
- Success. The requested resource has been created on the server, e.g. an uploaded file.
400 Bad Request:
- We didn't understand something about your request, for instance you asked for an invalid or unsupported response format.
- We understood the request, but access was not allowed. Usually this means a secure URI was not accessed over SSL.
404 Not Found:
- There was no service or method located at the URI you provided. Note that 404 errors are handled a bit differently in that they will pass an HTTP status code and an HTML error response instead of a response in the format requested.
405 Method Not Allowed:
- An invalid HTTP method for the URI was passed. For instance, the HTTP method provided was
DELETEbut the operation performed by the URI only accepts
500 Internal Server Error:
- Something unknown went wrong, see the message returned for additional details. This may mean something is broken on our end or a required parameter was not passed in to a method.
502 Bad Gateway:
- A resource used by the method, such as a database or LDAP server, is currently down or the request timed out while trying to access it.
In addition to an HTTP status code issued in the response, an error message will be provided in the format specified by your request (404 errors being the lone exception).