What we do
Tools
Industries
Department
How we workLet's talk →
Home/Plaid/Plaid API
Plaid

The Plaid API: How the Tokens Work, Which Product You Need, and Going Live

Plaid's API is a set of separate products behind one connection flow. A user links their bank in Plaid Link, your server swaps a short-lived token for a permanent one, and you call whichever products you've enabled: Auth, Identity, Transactions, Investments or Income. Here's the flow, a map of the products, and what's different once real banks are on the other end.

The token flow every call depends on

1. Your server calls /link/token/create and hands the link_token to your front end.

2. The user picks their bank and signs in inside Plaid Link. On success you get a public_token, which expires after 30 minutes.

3. Your server exchanges it at /item/public_token/exchange for an access_token and item_id. The access token doesn't expire, so store it like a password and never send it to the browser.

4. Call the products with that access token, for example /auth/get or /transactions/sync. One Item is one login at one bank, which can cover several accounts.

Which Plaid product answers your question

Most integrations need one or two of these. Plaid bills per product, so pick by the question, not the list.

You need to Use Plan for
Get an account and routing number before an ACH debit Auth (/auth/get) Not every bank supports instant Auth. Plaid's micro-deposit fallback works, but adds days and a step for the user.
Check the account belongs to the person in front of you Identity, or Identity Match to score it against the details you hold Joint and business accounts often carry a different name from the one typed into your form. Decide your threshold before launch.
See what moved through an account Transactions (/transactions/sync) 90 days of history by default, up to 730 if you ask for more with days_requested when the user links.
Read holdings in investment accounts Investments A narrower product. Coverage depends on the institution.
Verify income for a loan or a lease Income, from bank deposits or payroll data Usually reviewed by a person afterwards, so think about how the result reaches them.
Move the money as well as check the account Plaid Transfer, or a processor token for a payments partner such as Stripe Transfer moves real funds and has its own approval. A processor token keeps account numbers out of your systems.

Plaid's sandbox next to Production

The Quickstart gets you a working Link flow fast. These are the differences that make Production a separate piece of work.

Sandbox

Test data, free

  • Sign in to any test bank with user_good and pass_good.
  • Fire webhooks on demand with /sandbox/item/fire_webhook, and force a broken login with /sandbox/item/reset_login.
  • Data is tidy and arrives straight away.
Production

Real banks, real users

  • You apply for access and Plaid reviews your company and use case. Billing starts per product.
  • Big banks connect through OAuth, so the Link flow looks different from the sandbox one. Test them specifically.
  • History takes time to arrive, logins expire, and users pick the wrong account.

Plaid's old Development environment was shut down in June 2024. Real-data testing now happens in Production, and teams created since 15 April 2026 start on a Trial plan rather than Limited Production.

What a live Plaid integration has to handle

None of these appear in the Quickstart. All of them show up in the first month with real users.

The first transactions call comes back empty

How you'll know: A user just linked their bank and your app shows no history.

Fix: Plaid needs time to fetch transactions. Wait for the SYNC_UPDATES_AVAILABLE webhook, then sync. The first recent transactions usually arrive before the full history, so show what you have and say more is coming.

Pending transactions duplicate or vanish

How you'll know: A purchase appears twice, or disappears and comes back with a new ID.

Fix: /transactions/sync returns added, modified and removed lists. A pending transaction is removed when it posts and a new one is added. Apply all three lists, and save the cursor only after the page is stored.

A bank login stops working

How you'll know: Calls return ITEM_LOGIN_REQUIRED after the user changed their password or their consent ran out.

Fix: Send them back through Link in update mode, created with their existing access token. Without a prompt in your app, that user's data simply goes stale.

Webhooks taken on trust

How you'll know: Your endpoint acts on any request that reaches it.

Fix: Plaid signs each webhook in the Plaid-Verification header as a JWT. Check it with the key from /webhook_verification_key/get before you act.

The wrong account gets debited

How you'll know: A user links their bank and you debit the savings account, not the checking account they meant.

Fix: An Item can return several accounts. Let the user choose one in Link, or filter by account type, and store the chosen account_id alongside the access token.

Customers leave, access tokens stay

How you'll know: Old Items keep running up product charges and holding data you no longer need.

Fix: Call /item/remove when a customer closes their account or withdraws consent.

Questions people ask

What does the Plaid API actually let you build?

Bank connections and the data behind them. Auth gives account and routing numbers, Identity checks the account holder, Transactions returns history, Investments returns holdings and Income verifies earnings. Transfer and processor partners cover moving the money. Most products need one or two of these.

What is Plaid Auth used for?

Getting a verified account and routing number when a user links their bank, so you can set up an ACH debit without asking them to type numbers in or waiting on manual micro-deposits. For banks without instant Auth, Plaid offers a micro-deposit fallback.

How do I move from Plaid's sandbox to real bank connections?

Apply for Production access from the Plaid Dashboard. Plaid reviews your company and how you'll use the data, and some products need their own approval. Then swap your sandbox secret for the Production one and test with real accounts, including a big OAuth bank, before launch.

Can Plaid pull investment account data too?

Yes, through Investments, which returns holdings and investment transactions for linked brokerage and retirement accounts. It's used far less than Auth or Transactions, and coverage depends on the institution.

What does Plaid's Quickstart actually include?

A sample app with a front end and a back end that runs the whole Link flow against the sandbox: create a link token, link a test bank, exchange the token and call a product. It's the fastest way to see the moving parts before you build your own.

Does a Plaid access token expire?

No, but it can stop working. If the user changes their bank password or their consent lapses, the Item needs updating through Link's update mode. You can also rotate a token with /item/access_token/invalidate or revoke it with /item/remove.

Is the Plaid sandbox free?

Yes. The sandbox uses test data only and costs nothing. Charges begin in Production, per product, so it's worth knowing which products you need before you apply.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.