Error codes
| Code | Meaning | Charged |
|---|---|---|
200 | Successful query | Yes |
402 | Payment absent, invalid, or insufficient | No |
400 | Malformed request or missing required fields | No |
404 | Case not found in the specified court | No |
422 | Court code not recognized or not currently covered | No |
429 | Rate limit exceeded | No |
503 | PACER or CM/ECF temporarily unavailable | No |
504 | Query timeout | No |
500 | Internal server error | No |
Handling errors
Rate limits
| Limit | Value |
|---|---|
| Requests per minute | 60 per wallet |
| Requests per day | 10,000 per wallet |
retry_after field (in seconds) indicating when the limit resets. For portfolios requiring more than 10,000 daily queries, distribute load across multiple funded wallets.
PACER availability
DocketLayer’s data depends on PACER and CM/ECF availability. During PACER maintenance windows, affected courts return 503 responses. The/v1/status endpoint reflects known maintenance windows and is the best source for current system state.
Common mistakes
Wrong court code — Use the court code exactly as listed in/v1/status. Common examples: nysd, deb, cand. Do not include .uscourts.gov or any other suffix.
Wrong case ID format — Federal case numbers follow the pattern division:year-type-number. Example: 1:24-cv-01234. See the case ID format guide.
Depleted wallet — A $0 USDC balance causes all queries to return 402. Monitor your wallet balance and refund before it runs dry.
Uncovered court — Querying a court not in the current coverage list returns 422. Always check /v1/status first.