Obtain a PACER session token via the Authentication API for use in downstream PCL and CM/ECF API calls

domain: pacer.uscourts.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. POST to https://pacer.login.uscourts.gov/services/cso-auth with Content-Type: application/json and a JSON body containing loginId, password, and an optional clientCode
  2. Parse the response and extract the returned authentication token string
  3. Store the token to use as the X-NEXT-GEN-CSO header value in all subsequent PACER API requests
  4. When the token expires, detect the refreshed token returned in the response headers of any PACER API call and update the stored value; or re-POST to cso-auth to get a fresh token
  5. For QA and testing use https://qa-login.uscourts.gov/services/cso-auth with a separate PACER QA account

Known gotchas

Related routes

Obtain and manage a NextGen CSO authentication token for the PACER Case Locator (PCL) API, including reuse and invalidation, rather than re-authenticating on every search
pacer.uscourts.gov · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans