Company Litigation Coverage Dossier
Pricing
from $24.50 / 1,000 coverage dossiers
Combine litigation search datasets into company-query coverage dossiers. Separate case mentions, completed searches and missing jurisdiction evidence for a traceable review queue.
You can access the Company Litigation Coverage Dossier programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in API & Integrations in Apify Console.
# Set API token$API_TOKEN=<YOUR_API_TOKEN>
# Prepare Actor input$cat > input.json << 'EOF'<{< "items": [< {< "recordType": "match_observation",< "schemaVersion": "1.0.0",< "found": true,< "partial": false,< "failureType": null,< "checkedAt": "2026-09-22T05:25:29.359Z",< "observedAt": "2026-09-22T05:25:29.359Z",< "company": "Tesla",< "jurisdiction": "PL",< "caseCount": 23,< "cases": [< {< "name": "III K 14/12",< "court": "Sąd Okręgowy w Jeleniej Górze",< "date": "2012-12-04",< "number": "III K 14/12",< "url": "https://www.saos.org.pl/judgments/12947",< "signal": "fulltext-mention"< },< {< "name": "KIO 2272/11",< "court": "NATIONAL_APPEAL_CHAMBER",< "date": "2011-11-03",< "number": "KIO 2272/11",< "url": "https://www.saos.org.pl/judgments/119124",< "signal": "fulltext-mention"< },< {< "name": "KIO 808/12",< "court": "NATIONAL_APPEAL_CHAMBER",< "date": "2012-05-07",< "number": "KIO 808/12",< "url": "https://www.saos.org.pl/judgments/120176",< "signal": "fulltext-mention"< },< {< "name": "KIO 1174/12",< "court": "NATIONAL_APPEAL_CHAMBER",< "date": "2012-06-22",< "number": "KIO 1174/12",< "url": "https://www.saos.org.pl/judgments/120463",< "signal": "fulltext-mention"< },< {< "name": "KIO 1812/12",< "court": "NATIONAL_APPEAL_CHAMBER",< "date": "2012-09-07",< "number": "KIO 1812/12",< "url": "https://www.saos.org.pl/judgments/120946",< "signal": "fulltext-mention"< },< {< "name": "KIO 623/13",< "court": "NATIONAL_APPEAL_CHAMBER",< "date": "2013-04-16",< "number": "KIO 623/13",< "url": "https://www.saos.org.pl/judgments/122283",< "signal": "fulltext-mention"< },< {< "name": "KIO 2060/13",< "court": "NATIONAL_APPEAL_CHAMBER",< "date": "2013-09-10",< "number": "KIO 2060/13",< "url": "https://www.saos.org.pl/judgments/123419",< "signal": "fulltext-mention"< },< {< "name": "KIO 2907/13",< "court": "NATIONAL_APPEAL_CHAMBER",< "date": "2014-01-08",< "number": "KIO 2907/13",< "url": "https://www.saos.org.pl/judgments/124062",< "signal": "fulltext-mention"< },< {< "name": "KIO 327/14",< "court": "NATIONAL_APPEAL_CHAMBER",< "date": "2014-03-05",< "number": "KIO 327/14",< "url": "https://www.saos.org.pl/judgments/124432",< "signal": "fulltext-mention"< },< {< "name": "KIO 1197/14",< "court": "NATIONAL_APPEAL_CHAMBER",< "date": "2014-06-26",< "number": "KIO 1197/14",< "url": "https://www.saos.org.pl/judgments/161581",< "signal": "fulltext-mention"< }< ],< "sourceNote": "Poland — SAOS full-text judgment search (signal:\"fulltext-mention\", a keyword hit, not a confirmed party). Ingestion lags real court activity by months. 23 full-text match(es); showing up to 10.",< "__source": {< "actor": "zinin/litigation-check",< "actorId": "ybyRD5b0ztnevr87N",< "runId": "KE1BPmEJSzcdNUavX",< "datasetId": "LEvmLfGfnRj6PGBeQ",< "sampleRowIndex": 0,< "projection": "Public business-record fields only; observed values unchanged. Added __source is provenance, not upstream payload."< }< }< ]<}<EOF
# Run the Actor using an HTTP API# See the full API reference at https://docs.apify.com/api/v2$curl "https://api.apify.com/v2/actors/zinin~company-litigation-coverage-dossier/runs?token=$API_TOKEN" \< -X POST \< -d @input.json \< -H 'Content-Type: application/json'Below, you can find a list of relevant HTTP API endpoints for calling the Company Litigation Coverage Dossier Actor. For this, you’ll need an Apify account. Replace <YOUR_API_TOKEN> in the URLs with your Apify API token, which you can find under API & Integrations in Apify Console. For details, see the API reference.
https://api.apify.com/v2/actors/zinin~company-litigation-coverage-dossier/runs?token=<YOUR_API_TOKEN>Note: By adding the method=POST query parameter, this API endpoint can be called using a GET request and thus used in third-party webhooks. Please refer to our Run Actor API documentation.
https://api.apify.com/v2/actors/zinin~company-litigation-coverage-dossier/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>Note: This endpoint supports both POST and GET request methods. However, only the POST method allows you to pass input data. For more information, please refer to our Run Actor synchronously and get dataset items API documentation.
https://api.apify.com/v2/actors/zinin~company-litigation-coverage-dossier?token=<YOUR_API_TOKEN>For more information, please refer to our Get Actor API documentation.
Actors can be used to scrape web pages, extract data, or automate browser tasks. Use the Company Litigation Coverage Dossier API programmatically via the Apify API.
You can choose from:
You can start Company Litigation Coverage Dossier with the Apify API by sending an HTTP POST request to the Run Actorendpoint. An Actor’s input and its content type can be passed as a payload of the POST request, and additional options can be specified using URL query parameters. The Company Litigation Coverage Dossier is identified within the API by its ID, which is the creator’s username and the name of the Actor.
When the Company Litigation Coverage Dossier run finishes you can list the data from its default dataset(storage) via the API or you can preview the data directly on Apify Console.