Traverse all cards in board through RESTapi

[Dannie Hansen]

Hi,

I'm the author of a powerup Activity timer that has data export functionality. This functionality relies upon accessing all of the cards of the board through the following REST API:

https://api.trello.com/1/boards/{{BOARD}}/cards/all?pluginData=true&fields=id,idList,name,desc,labels,pluginData,closed&key={{KEY}}&token={{TOKEN}}

I'm curerently experiencing that it will throw 403 for some users when there is too many cards. Looking at the documentation it does not appear that there is any pagination for this API. I've tried some that is used on other APIs (query parameters) such as limit and page. Limit works, but page does not.

Are there any undocumented ways of paginating the results off of cards/all API so that i can query all of the cards on the board?

[Rasmus Wulff Jensen]

Not real pagenation as such, but you could instead get all lists on the board and the get all cards on each list as a sort of pagenation 

[Dannie Hansen]

Hi @Rasmus Wulff Jensen ,

Thanks.

Checking the API documentation https://developer.atlassian.com/cloud/trello/rest/api-group-lists/#api-lists-id-cards-get it doesn't appear this RESTapi supports pagination or filtering. Since i need access to closed/archived cards, then this may be a problem for my particular usecase.

[Rasmus Wulff Jensen]

Yea... That would be a problem... And I've also just checked and limit is the only option there is... 

How about splitting the request into two... One for all the open cards and one for all the closed cards (instead or the "/all")? ...

[Dannie Hansen]

@Rasmus Wulff Jensen That is a good idea. Querying each of the different types with the limit set to the max.

Then i could simply display a disclaimer to the user if any such limits are hit that they may be missing data.

I'll leave the topic open in case anything else pops up from others that may further help resolve it. But at least this would make it usable for a time (until those limits are hit) for people with many cards.