1. Documentation
  3. Get started
  5. Errors
Open Specter
  • Introduction
  • Quickstart
  • Authentication
  • Errors
  • Rate limits
  • Best practices
  • Overview
  • Best practices
  • Create a key
  • Read and write
  • Overview
  • Best practices
  • Hosted page
  • Submit from your code
  • Drafts, files and corrections

Errors

Every refusal is JSON with one sentence a person can act on.

Loading documentation…

Authentication< PreviousRate limitsNext >

On this page

Refused batchesMalformed bodies

A refused request answers a status and one sentence that says what was wrong and how to fix it:

json
{"error": {"message": "invalid value — Amount: not a number"}}
StatusMeaning
400The request is wrong. The sentence names the field or column and what was wrong.
401No key, or an unknown or revoked one.
402The route needs a plan the workspace is not on.
403The key was not given the scope this route needs — e.g. this key was not given rows:write.
404Nothing at that id, or nothing this key may see.
429Too many requests. Wait the Retry-After seconds.
5xxOur side. Retry with backoff; quote the answer's X-Request-Id header to support.

Refused batches

A batch that is refused lists every bad item by its position, and writes nothing:

json
{"error": {  "message": "1 of 2 rows were refused and nothing was written — …",  "errors": [{"index": 1, "message": "invalid value — Amount: not a number"}]}}

Malformed bodies

When the body itself can't be read, the refusal also carries expected — the shape the route takes — so you can compare it with what you sent.