Skip to main content
The Plaid API in Sandbox, for agents that link bank accounts, read balances and ACH numbers, or keep a ledger in step with Transactions Sync. Plaid’s own Sandbox is real but uncooperative: its Items update on their own schedule, a pending charge posts when it posts, and an ITEM_LOGIN_REQUIRED or a BALANCE_LIMIT cannot be summoned for a test. This twin answers with Sandbox’s own envelopes, token shapes and replay rules, and moves when the environment advances. Slug: plaid

​
What it models

Advancing the environment delivers a fresh Item’s history, completes a refresh, posts pending transactions (the pending one is removed, the posted one added with pending_transaction_id) and repairs an Item waiting on its user to log back in. Directives — set_item_error, set_rate_limit, set_product_ready, queue_transaction_change, set_sync_mutation — create the states no Sandbox call can.

​
Not modelled

Identity, Investments, Liabilities, Assets, Income, Transfer, Signal, Payment Initiation, processor tokens, Enrich, Consumer Report, Beacon, Monitor, Identity Verification, institutions search, webhook delivery, Link’s browser UI and any test user or institution other than user_good at ins_109508. Merchant enrichment of Sandbox-created transactions comes back null. An operation Plaid has that the twin has not built answers an explicit 501 with error_code: NOT_MODELLED, never a plausible response; a path Plaid does not have gets Plaid’s own 404 NOT_FOUND.