← All breaking-change reports

Plaid breaking change: 43.0.0: Merge pull request #717 from plaid/generated_20260625T191121Z

plaid · breaking · 2026-06-25 · upstream source

What changed

report_requested -> reports_requested; protect_results removed; /item/handle_fraud_report removed

From the upstream announcement:

OpenAPI generated code at 2026-06-25T19:11:21Z

Who is affected

The only edit that affects running integrations is the /cra/check_report/verification/pdf/get request field: rename report_requested to reports_requested and wrap the scalar value in an array.

To find out whether your repo is hit — file and line number, no code leaving your machine:

npx mendapi scan --repo .

How to fix it

mendapi ships a deterministic migration pack for this change (plaid-node-v43-v44-breaking-renames). Preview the patch locally (dry-run is the default; nothing is modified without --apply):

npx mendapi fix --repo . --migration plaid-node-v43-v44-breaking-renames

The pack is idempotent, gold-regression tested, and safe on partially migrated code.

What the migration does:

The only edit that affects running integrations is the /cra/check_report/verification/pdf/get request field: rename report_requested to reports_requested and wrap the scalar value in an array. This is a deterministic key rename plus array-wrap at each call site. Reads of link session protect_results can optionally be deleted as dead code (the API stopped populating the field), but that is hygiene, not a break. The removed fraud-report endpoint had no customers, so no consumer migration exists for it.

Before:

await plaid.craCheckReportVerificationPdfGet({ report_requested: 'VOE' });

After:

await plaid.craCheckReportVerificationPdfGet({ reports_requested: ['VOE'] });

Detected and tracked by mendapi — Dependabot for every API you depend on. Scans run locally; your code never leaves your machine.

Related

Pre-release. Change data is recorded from upstream provider releases, changelogs and OpenAPI spec diffs; every article links its source.