Paystub not returning verification as required param for constructor
Closed this issue · 2 comments
client.income_verification_paystubs_get() no longer returns a "verification" object as part of its payload. This is breaking the api client for attempts to get paystub data.
You can see here...
https://github.com/plaid/plaid-python/blob/9.9.0/plaid/model/paystub.py#L151
... that verification is still a required parameter even on the newest client. When it doesn't come back from the api call everything breaks.
Used to look something like this when it came back:
{
"document_metadata": [
{
"doc_id": "2jkflanbd",
"doc_type": "DOCUMENT_TYPE_PAYSTUB",
"name": "paystub.pdf",
"status": "DOCUMENT_STATUS_PROCESSING_COMPLETE"
}
],
"paystubs": [
{
"deductions": {
"breakdown": [
{
...
}
],
"total": {
...
}
},
"doc_id": "2jkflanbd",
"earnings": {
"breakdown": [
{
...
},
{
...
}
],
"total": {
...
}
},
"employee": {
"address": {
...
},
"name": "ANNA CHARLESTON",
"taxpayer_id": {
...
}
},
"employer": {
"name": "PLAID INC",
"address": {
...
}
},
"net_pay": {
...
},
"pay_period_details": {
"distribution_breakdown": [
...
],
...
},
"verification": {
"verification_status": "PAYSTUB_VERIFICATION_STATUS_VERIFIED",
"verification_attributes": []
}
}
],
"request_id": "2pxQ59buGdsHRef"
}
"verification" is no longer in the payload and it is breaking the api.
Any assistance would be much appreciated.
@anonymoose thank you for the report. This should be resolved the week after next, when our next scheduled client library release comes out -- if this is causing issues for you that can't wait that long to resolve, please let me know!
@anonymoose with the latest client libraries released yesterday, this should now be resolved.