General

Errors

Common error scenarios and responses

Error Responses

All error responses will follow the following format with a top-level error object and a 4XX status code.

1{
2  "error": {
3    "type": "<error type>",
4    "message": "<error message>"
5  }
6}

Invalid Auth Token

Using an auth token that does not exist or is incorrect will result in a 404 response status.

$curl --request GET \
>  --url https://api.glideapps.com/tables \
>  --header 'Authorization: Bearer INVALID'
1{
2  "error": {
3    "type": "request_error",
4    "message": "API key not found, or duplicate IN****ID"
5  }
6}

Invalid Stash ID or Serial

Using a stash ID or serial that does not meet the requirements will result in a 400 response status.

$curl --request PUT \
>  --url https://api.glideapps.com/stashes/-INVALID-/1 \
>  --header 'Authorization: Bearer VALID-API-KEY'
1{
2  "error": {
3    "type": "request_validation_error",
4    "message": "Invalid request params: Stash ID must be 256 characters max, alphanumeric with dashes and underscores, no leading dash or underscore"
5  }
6}

Invalid Row Data

When adding or updating rows in a table, if the row data does not match the table schema, the API will return a 422 response status.

Unknown Column

1{
2    "error": {
3        "type": "column_id_not_found",
4        "message": "Unknown column ID 'foo'"
5    }
6}

Invalid Value for Column

1{
2    "error": {
3        "type": "column_has_invalid_value",
4        "message": "Invalid value for column 'foo'"
5    }
6}

Row Not Found

When attempting to update a row that does not exist, the API will return a 404 response status.

1{
2    "error": {
3        "type": "row_not_found",
4        "message": "Row with ID 'XHz6kF2XSTGi1ADDbryjqw' not found"
5    }
6}