Errors | Tradespace | Developer Documentation

The API reports errors in two ways, depending on where the request fails.

Request errors

If the request is rejected before the query runs, the API returns an HTTP error status.

Status	Meaning
`400 Bad Request`	The request has no operation name. Name the query and send the name in `operationName`.
`401 Unauthorized`	The API key is missing, unknown, or inactive, or it was created in a different region than the endpoint.
`429 Too Many Requests`	The hourly rate limit is exhausted. See Rate limits.

A 400 response has an errors array, like a GraphQL error:

{
  "errors": [
    {
      "message": "Operation name is required",
      "extensions": { "status": 400 }
    }
  ]
}

401 and 429 responses have an error object:

{
  "error": {
    "message": "The API key is missing, invalid, or inactive",
    "code": 401,
    "status": "unauthorized"
  },
  "meta": {
    "timestamp": "2026-10-02T11:37:57Z",
    "api_version": "v1",
    "request_id": "d4fb189d-9dcb-4f33-beb4-bee8870fb07c"
  }
}

Include the request_id when you contact Tradespace support about a failed request.

GraphQL errors

Once the query runs, the response is 200 OK even when part of it fails. Failures appear in the errors array. Each error’s extensions.status holds an HTTP-style status. A failing field that can be null resolves to null. Single-record queries such as disclosure or patent cannot be null, so when one of them fails the whole data value is null.

`extensions.status`	Meaning
`400`	An argument is invalid, for example a `sortField` the query does not support. The message lists the allowed values.
`403`	Your account is not allowed to read this record or module.
`404`	No record matches the ID or number you passed.

{
  "data": null,
  "errors": [
    {
      "message": "Disclosure not found",
      "extensions": { "status": 404 }
    }
  ]
}

Always check errors before reading data.