Errors and pagination

Errors

All endpoints use the same error shape:

{
  "error": "Not Found",
  "message": "The requested filing was not found.",
  "request_id": "req_01J..."
}

Status	Meaning
400	Invalid parameter combination
401	Missing or invalid API key
403	Insufficient permission
404	Resource not found
422	Request schema validation failed
429	Rate limit exceeded
503	Source content is temporarily unavailable or still processing

Include request_id when contacting support.

Pagination

Paginated collection endpoints accept limit and offset and return pagination in meta:

{
  "filings": [],
  "meta": {
    "jurisdiction": "US",
    "count": 100,
    "limit": 100,
    "offset": 0,
    "next_offset": 100,
    "as_of": "2026-07-20T23:59:59Z"
  }
}

Pass next_offset as the next request’s offset. A null value means there are no more records. Keep the same as_of value across pages when you need a stable point-in-time result set.