Plaid API
- API version 2020-09-14
Vendor coverage
Plaid API changes & breaking changes
Plaid publishes its API as an OpenAPI spec and versions it with dated releases. Detektu diffs every revision, because in a financial data integration a silently changed field is a reconciliation incident waiting to happen.
Coverage
What Detektu monitors
Official products and contracts checked for changes.
Change model
How Plaid ships changes
The release patterns that shape your integration risk.
Plaid's dated API versions gate breaking changes, but the spec still moves continuously: new products, new webhook payloads, extended enums on transaction categories. Financial integrations tend to consume a narrow, critical slice of that surface.
Detektu reports every change with exact evidence and lets you declare the endpoints and fields your ledger logic depends on, so enum extensions you don't parse stay informational while changes under your reconciliation path escalate.
From change to finding
Findings you'd see
Illustrative examples. Every real finding carries exact before/after evidence, severity, and source provenance.
Field removed from the transactions response
openapi:POST /transactions/get ::response.200.transactions.category_idNew webhook payload variant documented
openapi:webhook:TRANSACTIONS ::sync_updates_availableMonitored for you
Do Plaid's changes affect your integration?
Choose the operations and fields your services use. Detektu matches Plaid findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.