Skip to main content
This walks through connecting one user and making your first call. Steps 1–3 acquire an access token. Step 4 uses it.
The interactive Run on the API reference pages calls the live endpoints with an access token you paste in. The token itself is obtained with the steps below.

Before you start

  • Have your client_id and client_secret handy (delivered per environment).
  • Make sure you have a working sandbox login (in the sandbox handoff document).

1. Generate a PKCE verifier and challenge

Keep the verifier for step 3. Fill in your client_id and the code_challenge from step 1, then Copy authorize URL and open it in a browser: Planning to use TIN verification? Tick the verify:tins box so your tokens carry that scope from the start; otherwise you can add it any time later by re-running authorize with the extra scope. Log in and consent to the requested scopes. You will be redirected to a fake callback url that looks something like this:
For now, just grab the code value and save it for step 3. For more information, see the Authorize reference.

3. Exchange the code for tokens

Open Get or refresh a token, select the authorization_code example, then fill in these values and Run it: The response includes an access_token. Use it in step 4.

4. Make your first call

Open Look up client account by EIN (or Look up taxpayer by EIN), paste your access_token as the bearer credential, send a sandbox EIN such as 11-1111111, and Run.
Your sandbox is preloaded with test businesses covering each compliance scenario. Your handoff document lists their EINs and what each one returns. Look a few up to see the different statuses, and see Lookup results for how to read the response.