A WireMock simulation of Plaid's REST API — covering user records, Layer session prefill, item association, data refresh, and third-party tokens.
A shared instance of this template runs on a public endpoint — call it right now from curl, an SDK, or an AI agent. Responses are fixed examples and behavior can't be changed; rate limits apply.
Jump to the endpoints ↓Run this template as a mock API in WireMock Cloud for a private instance you control — edit stubs, add stateful scenarios, use dynamic response templating, and inspect requests in the log.
Open in WireMock Cloud (free) →Live sandbox · no signup, no API key
A running WireMock Cloud instance of this template, callable right now from a terminal, a script, or an AI agent.
Endpoints
POST Create - /user/create
curl -s -X POST 'https://g8z79.wiremockapi.cloud/user/create' \
-H 'Content-Type: application/json' \
-d '{}'POST Static - /user/items/get
curl -s -X POST 'https://g8z79.wiremockapi.cloud/user/items/get' \
-H 'Content-Type: application/json' \
-d '{}'POST Static - /user/items/remove
curl -s -X POST 'https://g8z79.wiremockapi.cloud/user/items/remove' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — The Plaid API (2020-09-14_1.688.6) · 15 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /user_account/session/event/send | Send User Account Session Event |
| POST | /user_account/session/get | Retrieve User Account |
| POST | /user/create | Create user |
| POST | /user/financial_data/refresh | Refresh user items for Financial-Insights bundle |
| POST | /user/get | Retrieve user identity and information |
| POST | /user/identity/remove | Remove user identity data |
| POST | /user/items/associate | Associate Items to a User |
| POST | /user/items/get | Get Items associated with a User |
| POST | /user/items/remove | Remove Items from a User |
| POST | /user/products/terminate | Terminate user-based products |
| POST | /user/remove | Remove user |
| POST | /user/third_party_token/create | Create a third-party user token |
| POST | /user/third_party_token/remove | Remove a third-party user token |
| POST | /user/transactions/refresh | Refresh user items for Transactions bundle |
| POST | /user/update | Update user information |
Unauthenticated WireMock Cloud demo sandbox for Plaid — not an official Plaid sandbox, and it returns simulated example data only.
Fifteen endpoints manage the user records that Layer and Plaid Check hang off, and the user store operates for real — with one twist to absorb before anything else: it keys on user_id. /user/create issues a fresh id per call; present that id and /user/get, /user/update, and /user/remove all recognize it, with remove genuinely retiring it. Present only a user_token — the credential the production API expects on these routes — and the answer is USER_NOT_FOUND. Two personas share the instance by design: the session route serves the Layer prefill payload, a complete identity with an SSN and per-field edit-history counters, while stored user records read back as a second persona built for multi-contact parsing.
The store indexes user_id values and only those. It's the one place this sandbox diverges from production addressing, where user_token is what these routes take — so put the id from /user/create in the user_id field and the lifecycle runs end to end. Treat the difference as a convention of this instance, not a fact about the API.
The session route's identity — SSN, Pawnee address, edit counters — is the payload Layer hands an app to prefill onboarding. The stored user record is a different, deliberately fuller persona: two emails, two phone numbers, primary flags set, the plural shape contact-merging code needs. They coexist because they model different objects, not the same person twice.
Fraud heuristics. How often identity fields change — current, one-day, thirty-day, and lifetime windows — is core signal for synthetic-identity detection, and the fixture pins a profile with a recent address edit so exactly that logic has something to flag.
With a session token, which is minted in the Link & Tokens template — its Layer surface wraps a link token in the session envelope. Open the session there, then manage the resulting user records here; the pair covers Layer's front and back halves.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.