API template library

Plaid Identity mock API and live sandbox

A WireMock simulation of Plaid's REST API — covering account-holder identity, match scoring, document uploads, and refresh.

Vendor
Plaid
Functionality
Identity data and match scores
Spec version
2020-09-14_1.688.6
Endpoints
4
Stubs
4
Protocol
REST
Validation
AI-validated Before publication, an AI agent exercised these endpoints against the real Plaid API through WireMock's recording proxy, and the recorded traffic was used to verify each stub's request and response shapes.

Live sandbox · no signup, no API key

Plaid Identity

A running WireMock Cloud instance of this template, callable right now from a terminal, a script, or an AI agent.

Base URL
https://o9d97.wiremockapi.cloud

POST Get Identity

curl -s -X POST 'https://o9d97.wiremockapi.cloud/identity/get' \
  -H 'Content-Type: application/json' \
  -d '{}'

POST Match Identity

curl -s -X POST 'https://o9d97.wiremockapi.cloud/identity/match' \
  -H 'Content-Type: application/json' \
  -d '{}'

POST Get Identity Document Uploads

curl -s -X POST 'https://o9d97.wiremockapi.cloud/identity/documents/uploads/get' \
  -H 'Content-Type: application/json' \
  -d '{}'
Method Path Summary
POST /identity/documents/uploads/get Returns uploaded document identity
POST /identity/get Retrieve identity data
POST /identity/match Retrieve identity match score
POST /identity/refresh Refresh identity data

Unauthenticated WireMock Cloud demo sandbox for Plaid — not an official Plaid sandbox, and it returns simulated example data only.

What's inside the Identity template

The account holder here is Alberta Bobbeth Charleson — the same test persona Plaid's own sandbox institutions use — and /identity/get returns her as a proper owners object on the checking account: a names array, a home phone, a primary email, and a structured Malakoff, NY address. The companion /identity/match route scores an applicant against that record, answering with per-field scores and the boolean diagnostics beneath them — is_nickname_match, is_postal_code_match, is_business_name_detected — which is the layer onboarding risk logic actually branches on.

  • Identity data — the owners structure with plural names, phones, emails, and addresses
  • Match scoring — legal name, phone, email, and address scores with their diagnostic flags
  • Document uploads — /identity/documents/uploads/get returning upload metadata in account context
  • Refresh — the request_id-only acknowledgement that kicks off a re-pull

Frequently asked questions

Plaid's identity schema allows joint accounts and multiple contact points, so names, emails, phone_numbers, and addresses are all plural, each address wrapped in a data object with a primary flag. Parsers written against a single flat name break on real responses — the fixture's shape keeps that mistake from surviving a test run.

Not on this instance; every field reports a perfect score with benign flags. Threshold logic — treat 85 as a review case, fail on a postal mismatch — belongs against a WireMock Cloud copy where each score is an editable stub value instead of a constant.

Yes — Alberta Bobbeth Charleson, accountholder0@example.com, and the 2992 Cameron Road address are the identity Plaid's test institutions return, so fixtures and assertions written here transfer directly to tests that later run against Plaid's own sandbox environment.

No — this product reads who owns an already-linked bank account. The KYC journey for someone with no linked account — document checks, selfie checks, watchlist screening — is the Identity Verification template, a much larger surface that models the verification lifecycle itself.

Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.