Legal

API terms of use

DocketLayer LLC · Effective date: April 15, 2026 · Last updated: April 15, 2026

1. Agreement

These API Terms of Use ("API Terms") govern your access to and use of the DocketLayer API at api.docketlayer.com. They are incorporated into and form part of the DocketLayer Terms of Service. By making any request to the API, you agree to these API Terms. In the event of a conflict, these API Terms govern with respect to API access.

2. API access

No account registration is required. Authentication is provided through the x402 payment protocol — successful payment of the per-query fee constitutes authorization to receive the requested data. Your Solana wallet address serves as your identifier for rate limiting and billing purposes. DocketLayer does not issue API keys.

3. Endpoints

EndpointPriceDescription
GET /v1/case $0.99 USDC Full normalized docket data with filing details for changed cases
GET /v1/monitor $0.99 USDC Lightweight change indicator — boolean response for polling workflows
GET /v1/status Free Current API status, covered courts, and system health

DocketLayer reserves the right to add, modify, deprecate, or remove endpoints at any time. We will provide advance notice of breaking changes through the /v1/status endpoint and the GitHub repository where operationally feasible.

4. Request parameters

Required parameters for /v1/case and /v1/monitor:

ParameterTypeDescription
case_idstringFederal case number in standard format — e.g. 1:24-cv-01234
court_codestringCourt identifier — e.g. nysd, deb, cand
last_checkedstringISO 8601 timestamp of your last successful query for this case

5. Response format

All responses are JSON. A successful /v1/case response includes: case_id, court_code, changed (boolean), last_checked, checked_at, and new_filings (array of filing objects, empty if changed is false). Each filing object includes: filing_type, description, filed_at, filed_by, and document_number.

The API returns docket entry metadata only. It does not return the full text or content of court documents. To access document content, access PACER directly at pacer.uscourts.gov.

6. Data limitations

Read these limitations carefully before integrating. They affect how and whether DocketLayer data can be relied upon in legal, financial, and compliance contexts.

6a. Data is not real-time

DocketLayer maintains a continuously updated cache with a maximum polling interval of 15 minutes per court under normal conditions. Data may lag behind the official PACER record, and potentially longer during PACER maintenance or outages. DocketLayer is not a real-time feed.

6b. Data is not certified or official

Data returned by the API is provided for informational and monitoring purposes only. It is not a certified court record and is not a substitute for direct PACER access. Do not use API data as the authoritative source in any legal proceeding, regulatory filing, or compliance certification.

6c. Data may contain errors

PACER source data may contain errors or omissions. DocketLayer's normalization layer may introduce additional errors. Always verify critical information directly with the relevant court or through official PACER access.

6d. Coverage is limited

The API covers only the federal courts listed in our Coverage Roadmap. Queries for cases in uncovered courts return an error and are not charged. Check /v1/status for current coverage.

6e. Sealed and restricted cases

Cases that are sealed, restricted, or otherwise not publicly accessible through PACER will not be accessible through the API. The API returns an appropriate error for such cases.

6f. PACER dependency

The API is dependent on DocketLayer's ability to access PACER. PACER maintenance, outages, or access policy changes may affect API availability. DocketLayer is not responsible for interruptions caused by PACER or the federal judiciary.

7. Rate limits

LimitValue
Requests per minute60 per wallet
Requests per day10,000 per wallet

Requests exceeding these limits return a 429 response and are not charged. Systematic attempts to circumvent rate limits — through multiple wallets, IP rotation, or other means — are prohibited and may result in permanent suspension without refund.

8. Error responses

StatusMeaningCharged?
200Successful queryYes
402x402 payment challenge — handled by client libraryNo
400Malformed request or invalid parametersNo
404Case not found in covered courtsNo
429Rate limit exceededNo
503DocketLayer or PACER temporarily unavailableNo

9. Prohibited uses

10. Commercial use

You may use data returned by the API to build your own commercial products — AI agents, compliance tools, legal software, financial analytics — subject to these API Terms. You may not resell or redistribute raw API responses as a competing service without prior written permission. Contact [email protected] to discuss licensing arrangements.

When publicly displaying or publishing data derived from the API, you must not represent it as certified or authoritative court records.

11. Changes to the API

DocketLayer will endeavor to provide at least 30 days advance notice of breaking changes through the GitHub repository and /v1/status endpoint. DocketLayer is not liable for costs or damages arising from API changes following reasonable advance notice.

12. Liability

Your use of the API is subject to the limitation of liability provisions in the Terms of Service, incorporated by reference. DocketLayer's total liability arising from your use of the API shall not exceed the greater of (a) the total amount you paid in the 30 days preceding the claim, or (b) $100.00. DocketLayer is not liable for damages arising from your reliance on API data in any legal, financial, or compliance context.

13. Governing law

These API Terms are governed by the laws of the State of Wyoming, consistent with the Terms of Service.

14. Contact

API integration questions: [email protected]
Documentation: docs.docketlayer.com
System status: api.docketlayer.com/v1/status

DocketLayer LLC · Wyoming limited liability company · [email protected] · docketlayer.ai