Richard Testing around with this, it works just fine for me. The code below is my console output when going through the older_url values until it is null.
The only thing that I can confirm to be bugged is the CardCredit type since the order for those is off so you end up missing those completely.
> Round 1, only use the "count" option to get the 2 newest cards
GET: /v1/user/284741/card {"count":2}
Cards API response 1:
Card IDs: [460289,460227]
Pagination returned: {
"future_url": "/v1/user/284741/card?count=2&newer_id=460289",
"newer_url": null,
"older_url": "/v1/user/284741/card?count=2&older_id=460227"
}
> Round 2, use the count + older_id param to get the next 2 cards
GET: /v1/user/284741/card {"count":2,"older_id":460227}
Cards API response 2:
Card IDs: [227705,227468]
Pagination returned: {
"future_url": null,
"newer_url": "/v1/user/284741/card?count=2&newer_id=227705",
"older_url": "/v1/user/284741/card?count=2&older_id=227468"
}
> Round 3, use the count + older_id param to get the next 2 cards
GET: /v1/user/284741/card {"count":2,"older_id":227468}
Cards API response 3:
Card IDs: [101762]
Pagination returned: {
"future_url": null,
"newer_url": "/v1/user/284741/card?count=2&newer_id=101762",
"older_url": null
}