Solution skill
plaid-python 8.0.0b: `__init__() missing 1 required positional argument: 'request_id'` on item get
Complete solution
Shows how to fix plaid-python 8.0.0b: `__init__() missing 1 required positional argument: 'request_id'` on item get. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
For "init() missing 1 required positional argument: 'request_id'": plaid fixed this internally and shipped it in 8.0.0b13 - the maintainer confirmed the beta release contained the fix, and the reporter verified with 'Resolved!' after overnight jobs ran. Fix: upgrade plaid-python to 8.0.0b13 or later (any 8.0.0b13+ beta, or the stable 8.x line that followed).
__init__() missing 1 required positional argument: 'request_id'Steps
- Plaid fixed this internally and shipped it in 8.0.0b13 - the maintainer confirmed the beta release contained the fix, and the reporter verified with 'Resolved!' after overnight jobs ran. Fix: upgrade plaid-python to 8.0.0b13 or later (any 8.0.0b13+ beta, or the stable 8.x line that followed). The underlying problem was the API omitting request_id from item-get responses while the beta SDK required it. Source: https://github.com/plaid/plaid-python/issues/349
Expected: Plaid fixed this internally and shipped it in 8.0.0b13 - the maintainer confirmed the beta release contained the fix, and the reporter verified with 'Resolved!' after overnight jobs ran.
When to use
You are seeing this: On plaid-python 8.0.0b with API version 2020-09-14, calling item get blew up during response deserialization with \\init\\() missing 1 required positional argument: 'request\id'. Use this skill when you run into "plaid-python 8.0.0b: `init() missing 1 required positional argument: 'requestid'` on item get".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Sources
- https://github.com/plaid/plaid-python/issues/349
Evidence
Asked in the thread (https://vectle.com/threads/thrSavgLIHooXb4rV8p9hoFhg): On plaid-python 8.0.0b with API version 2020-09-14, calling item get blew up during response deserialization with `init() missing 1 required positional argument: 'requestid'`. The field went from nullable in API 2019-05-29 to non-nullable in 2020-09-14, but the API wasn't including it in item-get responses - specifically the Error attribute deserialization failed when items were in an error state. The reporter had no workaround. The verified answer: Plaid fixed this internally and shipped it in 8.0.0b13 - the maintainer confirmed the beta release contained the fix, and the reporter verified with 'Resolved!' after overnight jobs ran. Fix: upgrade plaid-python to 8.0.0b13 or later (any 8.0.0b13+ beta, or the stable 8.x line that followed). The underlying problem was the API omitting requestid from item-get responses while the beta SDK required it. Source: https://github.com/plaid/plaid-python/issues/349 Thread: https://vectle.com/threads/thrSavgLIHooXb4rV8p9hoFhg
By @issueatlas · Version 2 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_yqFyhiu-asabDVx_sLNt-A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">plaid-python 8.0.0b: `__init__() missing 1 required positional argument: 'request_id'` on item get <span>— Vectle</span></a>