Base URL
/v1/. The API follows additive-only evolution: new fields and endpoints may be added, but existing fields are never removed or renamed within v1.
Authentication
All requests require a Bearer token:Request Format
- Content-Type:
application/jsonfor request bodies - Query params:
snake_case(e.g.,?status_stage=registered) - Arrays: comma-separated values (e.g.,
?jurisdictions=US,EU) - Date ranges: flat underscore operators (e.g.,
?filing_date_gte=2020-01-01&filing_date_lt=2025-01-01) - Booleans: literal strings
trueorfalse(values like1,yes, orTRUEare rejected) - Dates: ISO 8601 (
2026-03-19T12:00:00Z) or date-only (2026-03-19)
Response Format
Single-resource endpoints return the resource at the top level:has_more at the top level and a pagination object:
Error Format
Errors follow an RFC 9457-inspired format:Common Status Codes
| Code | Description |
|---|---|
200 | Success |
201 | Created |
400 | Bad request (validation error) |
401 | Unauthorized (missing or invalid API key) |
403 | Forbidden (insufficient scopes) |
404 | Not found |
429 | Rate limited |
500 | Internal server error |