Error responses
If an API request is processed successfully, it returns the HTTP 200 status code. The HTTP code doesn’t indicate the response errors. For the list of any errors, you need to check the code in the response messages array.
If an API request is unable to process successfully, the FileMaker Data API returns:
-
an HTTP 400-level status code for standard HTTP errors
-
an HTTP 500-level status code for FileMaker errors
HTTP status code |
HTTP category |
Description |
---|---|---|
400 |
Bad request |
Occurs when the server cannot process the request because it is incomplete or invalid. |
401 |
Unauthorized |
Occurs when the client is not authorized to access the API. If this error occurs when attempting to log in to a database session, then there is a problem with the specified user account or password. If this error occurs with other calls, the access token is not specified or it is not valid. |
403 | Forbidden | Occurs when the client is authorized, but the call attempts an action that is forbidden for a different reason. |
404 | Not found | Occurs if the call uses a URL with an invalid URL schema. Check the specified URL for syntax errors. |
405 | Method not allowed | Occurs when an incorrect HTTP method is used with a call. |
415 | Unsupported media type |
Occurs if the required header is missing or is not correct for the request:
|
500 | FileMaker error | Includes FileMaker error messages and error codes. See "FileMaker error codes" in Claris Pro and FileMaker Pro Help. |
Notes
-
If the FileMaker Data API Engine is not running or cannot be reached, then error codes or messages returned are dependent on your web server (Apache or IIS).
-
For information about additional HTTP status codes returned, see www.w3.org.