Obtain an IRS API Client ID and configure certificate-based authentication for e-Services API access

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

Steps

  1. Complete Secure Access registration for e-Services for both the firm's principal and any delegated users who will use the API
  2. Generate a valid X.509 digital security certificate and a JWKS (JSON Web Key Set) file, since the Client ID application requires providing the JWKS for certificate validation
  3. Submit the API Client ID Application through the e-Services platform, associating it with the firm/organization and the specific API product needed (TIN Matching, Transcript Delivery System/SOR, IVES, or IRIS)
  4. Allow up to 45 calendar days for IRS processing, then sign in to retrieve the issued Client ID(s) for the firm
  5. Implement the ISP App authorization (JWT-based) flow in the application using the issued Client ID and configured certificate to authenticate subsequent API calls

Known gotchas

Related routes

Complete ID.me identity verification to register for IRS e-Services and gain access to systems such as the Transcript Delivery System and IRIS
irs.gov · 6 steps · unrated
Enroll in and call the IRS TIN Matching e-Services API for payee validation before 1099 filing
irs.gov · 6 steps · unrated
Authenticate to the ADP API using OAuth client_credentials flow with certificate-based mutual TLS
developers.adp.com · 5 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