Overview

Octo Table uses traditional HTTP error codes to indicate when requests succeeded or failed. Generally, most of our error responses are composed of the following parameters:

{
    "success": false,
    "error": {
        "code": "RESOURCE_NOT_FOUND",
        "message": "The specified table ID does not exist.",
        "class_name": "ResourceNotFoundException"
    }
}

Error Response Fields:

Field
Description

success

Indicates the nature of the response. For errors, this will always be "false".

error

Contains details about the specific error encountered.

code

A concise, machine-readable identifier for the error (e.g., RESOURCE_NOT_FOUND).

message

A brief, human-readable explanation of the error.

class_name

Error category or class name used by Octo Table system internally

HTTP Status Codes Used by Octo Table:

Status Code
Name
Description

200 OK

Success

The request was processed successfully.

201 Created

Resource Created

The request succeeded, and a new resource was created.

400 Bad Request

Invalid Request

The server could not process the request due to invalid or missing parameters.

401 Unauthorized

Authentication Required

Authentication credentials are missing or invalid.

403 Forbidden

Access Restricted

The client does not have the required permissions for this action.

404 Not Found

Resource Missing

The requested resource does not exist or could not be located.

409 Conflict

State Conflict

The request could not be completed due to a conflict with the resource’s current state.

500 Internal Server Error

Unexpected Error

An unexpected error occurred on the server.

503 Service Unavailable

Service Unavailable

The server is currently unable to handle the request due to temporary overloading or maintenance.

Last updated