I’m trying to get all the payouts that went to each bank account set up in my store for accounting reconciliation, so to help paginate my requests I’m trying to pull bankAccounts (first: 1) and then use the pageInfo for my next request, but it appears every bank account has a cursor of: "cursor": "e30="
I’ve observed the cursors are base64 encoded and that resolves to {}, based on the other objects I would’ve expected these to be base64 encoded of something like {id: <bank_account_id>, last_updated: <epoch time>} is this a known bug?
1 Like
Hi Nick,
I’ve looked into this with my test store and I haven’t been able to replicate this behaviour myself. In both cases when there is and is not more pages to paginate through, both the startCursor and endCursor does return expected id values when decoding the cursor string with Base64. I have not been able to replicate an empty object encoded cursor string like you’re experience.
Since I’m unable to replicate it on our end, we will need some additional details to be able to help look into this further with you.
Can you please share the following details from an example API call that returned the behaviour, and we can help look into it further.
- the myshopify.com URL of the store this occurred on
- the name of the app that made the API call
- the
x-request-id from the HTTP Response Headers of an example call that returns the unexpected cursor.