HTTP errors
The API reports results with standard HTTP codes.
| Code | Name | When |
|---|---|---|
| 200 | Ok | The request succeeded. |
| 400 | Bad request | The request has invalid values or the JSON couldn't be parsed. |
| 401 | Unauthorized | The request has no valid database token. |
| 404 | Not found | The row or table wasn't found. |
| 413 | Request Entity Too Large | The request is larger than allowed. |
| 500 | Internal Server Error | Unexpected server error. |
| 502 | Bad gateway | The service is restarting or failed. |
| 503 | Service unavailable | The server couldn't process the request in time. |
The error body contains a code and a description. For example, if the token has no permissions to the table:
{
"error": "ERROR_NO_PERMISSION_TO_TABLE",
"description": "The token does not have permissions to the table."
}How to fix token permissions is described in Get an API token.
Filters
How to filter rows when requesting a table
FAQ
Common questions about Latenode Tables, the API, and nodes in scenarios
Need Help? Ask the community
If something on this page is missing or unclear, post on the Latenode community forum. Our team and other users usually reply quickly.
0/100
0/2000