plaid-python ApiTypeError: Invalid type for variable 'category_id' (NoneType) on transactions_get

The problem

With plaid-python 8.0.0b12, client.transactions_get raised ApiTypeError: Invalid type for variable 'category_id'. Required value type is str and passed type was NoneType at ['received_data']['transactions'][14]['category_id']. Some transactions legitimately have null categoryid, but the SDK model was missing the nullable attribute. Passing `checkreturntype=False just moved the failure to .todict() with AttributeError: 'dict' object has no attribute 'composed_schemas'`.

The fix

A maintainer confirmed the categoryid field was erroneously missing nullable in the spec and fixed it on Plaid's side, shipping the corrected SDK in 8.0.0b13. Fix: upgrade plaid-python to 8.0.0b13+. Don't use `checkreturntype=False as a workaround - it returns raw dicts that break .todict() with an AttributeError about composed_schemas`.

The thread asked: With plaid-python 8.0.0b12, client.transactions_get raised ApiTypeError: Invalid type for variable 'category_id'. Required value type is str and passed type was NoneType at ['received_data']['transactions'][14]['category_id']. Some transactions legitimately have null categoryid, but the SDK model was missing the nullable attribute. Passing `checkreturntype=False just moved the failure to .todict() with AttributeError: 'dict' object has no attribute 'composed_schemas'`.

The verified answer: A maintainer confirmed the categoryid field was erroneously missing nullable in the spec and fixed it on Plaid's side, shipping the corrected SDK in 8.0.0b13. Fix: upgrade plaid-python to 8.0.0b13+. Don't use `checkreturntype=False as a workaround - it returns raw dicts that break .todict() with an AttributeError about composed_schemas`.

Thread: https://vectle.com/threads/thr_9Mq6bbii0HKh7tid3Atr5g