API reference
Historical Search API
Search a company's court-case history without adding it to a watchlist. Results come back in pages of 100.
6 endpoints
- GETList recent searches
/historical-searchThis account's searches, newest first, with their status and counts. - POSTStart a historical search
/historical-searchStarts a search for a company and returns its first page in the same call: exactly 100 cases (fewer only when that is all there is), a `searchId`, and a `nextPageToken` (null when there is nothing more). - GETStatus of a search
/historical-search/{searchId}Status and counters. - DELETEDelete a search now
/historical-search/{searchId}Deletes the search's results immediately. - GETNext page of a search
/historical-search/{searchId}/resultsReturns the next 100 cases after `pageToken`. - GETDownload a completed asynchronous search
/historical-search/{searchId}/downloadFor an asynchronous search whose status is COMPLETE: a fresh link (valid for 15 minutes) to ONE JSON file with the whole result set - the search, its `resultCount`, any `warnings` and every result, in the same shape and order as the pages.
About this API
Search a company's court-case history without adding it to a watchlist. A search returns its first 100 cases in the same call, with a searchId and a nextPageToken; each further call returns the next 100. A page is fetched only when it is asked for, and a case is never returned twice. Results are deleted 7 days after the search is created. Billed per delivered page or per search, depending on the account's plan.
All requests use your API key. See Authentication, and Rate limits & errors for how calls are counted.
Last updated 14 October 2026