Plaid API
POST /signal/decision/report changes: unknown client_transaction_id fails
Stopped workingSubscribe to Plaid APIShare
Calls to POST /signal/decision/report, body parameter client_transaction_id on Plaid API stopped working on September 1, 2025.
Calls it hits
POST /signal/decision/reportbody parameter client_transaction_id
In Plaid API's words
Beginning September 1, 2025, when /signal/decision/report or /signal/return/report is called with an unknown client_transaction_id (one that was never submitted to /signal/evaluate ), these endpoints will return an error instead of a success response.
Facts
Questions
When does this change take effect?
Calls to POST /signal/decision/report, body parameter client_transaction_id on Plaid API stopped working on September 1, 2025.
What happens to calls after September 1, 2025?
They have failed since September 1, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Plaid API 6
-
POST /signal/return/reportBehaviour change Stopped working -
POST /cra/monitoring_insights/*Endpoint removal Stops workingin 287 days -
No date
POST /credit/payroll_income/precheckEndpoint removal Deprecated, no date -
No date
POST /transfer/balance/getEndpoint removal Deprecated, no date -
No date
POST /cra/check_report/verification/pdf/getParameter removal Deprecated, no date -
No date
POST /payment_initiation/consent/createParameter removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.