A WireMock simulation of Plaid's REST API — covering credit-card, mortgage, and student-loan liability data.
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 Get Liabilities
curl -s -X POST 'https://7mdv3.wiremockapi.cloud/liabilities/get' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — The Plaid API (2020-09-14_1.688.6) · 1 endpoint
| Method | Path | Summary |
|---|---|---|
| POST | /liabilities/get | Retrieve Liabilities data |
Unauthenticated WireMock Cloud demo sandbox for Plaid — not an official Plaid sandbox, and it returns simulated example data only.
One endpoint is the whole product — /liabilities/get is all Plaid Liabilities offers in production too — and its payload carries three debt classes at once. The credit entry brings APR breakdowns, an overdue flag, and statement-cycle fields; the mortgage adds escrow balance, PMI and prepayment-penalty flags, interest rate, and maturity date; the student loan contributes a guarantor, disbursement dates, repayment status, and an expected payoff date. Each hangs off its own account fixture, so class-specific rendering code can route on type and subtype the way it would with a real Item.
A single-call product makes for the shortest possible plaid-python session — construct, request, read all three classes:
The response models deserialize cleanly in plaid-python 43, so this doubles as the quickest smoke test that your client, serialization layer, and network path all work — one request, three typed liability lists back.
Debt-focused features tend to hinge on rare field combinations — an overdue student loan, a mortgage without escrow — and those variants are most practical as edited stubs in your own WireMock Cloud copy, layered over the complete schema this fixture already provides.
import plaid
from plaid.api import plaid_api
from plaid.model.liabilities_get_request import LiabilitiesGetRequest
configuration = plaid.Configuration(
host="https://7mdv3.wiremockapi.cloud",
# required by the client, ignored by the mock
api_key={"clientId": "any-value", "secret": "any-value"},
)
client = plaid_api.PlaidApi(plaid.ApiClient(configuration))
resp = client.liabilities_get(
LiabilitiesGetRequest(access_token="access-sandbox-123")
)
liabilities = resp.liabilities
print(len(liabilities.credit), "credit,",
len(liabilities.mortgage), "mortgage,",
len(liabilities.student), "student")Yes, faithfully — Plaid ships Liabilities as a single route, and the template mirrors that instead of padding the catalog. The depth is vertical: the one response exercises parsers for three loan schemas, each with fields that appear nowhere else in the Plaid API.
The stub matches POST only, so a GET falls through to WireMock's no-match diagnostic — a 404 with a plain-text summary of the nearest stub — rather than anything Plaid-shaped. Plaid's convention of POSTing every read applies here as strictly as it does in production.
In this fixture, yes — one entry each, tied to a credit-card, a mortgage, and a student-loan account. Real Items usually surface a subset, so code should tolerate empty arrays; testing that tolerance means deleting a class from the stub in a private copy and watching nothing crash.
Balance figures ride along in the accounts array here, but the product built for balance freshness is the Accounts & Balance template — its credit-card fixture is the same one this template attaches APRs to, which keeps cross-template joins coherent.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.