Teable Web API follows HTTP status code semantics.
  • 2xx Represents success
  • 4xx Client errors
  • 5xx Server errors

Error responses will return a JSON-encoded body containing error and information fields. Here’s an example of an error response body:

{
  "message": "not allowed to operate space|read on spcxxxxxx",
  "status": 403,
  "code": "restricted_resource"
}

​
Success Status Codes

​
200 OK

The request has been successfully completed.

​
201 Created

The request has been successfully completed and a new resource has been created.

​
Error Codes

​
400 Bad Request

The request body cannot be parsed as JSON, or the input body parameters do not meet specification requirements.

​
401 Unauthorized

Unauthorized access to the API.

​
403 Forbidden

Attempting to access a protected resource with API credentials that lack the necessary permissions.

​
404 Not Found

Route or resource not found. This error is returned when accessing a non-existent resource path or when the request method doesn’t match.

​
500 Internal Server Error

The server encountered an unexpected condition.

​
503 Service Unavailable

The service is temporarily unavailable, possibly due to processing timeout or database connection failure.