Working Around Paginated JSON Data Sources?

We want to start using Bitbucket as a data source, so we can get metrics about our pull requests. Problem is, the Bitbucket API paginates, and returns a max of 100 objects per request.

Are there any known workarounds in Redash for getting all of the data?

The JSON data source is built for API’s that don’t enforce pagination limits. In your case, it would be best to add Bitbucket as a data source. That way the back-end can recursively fetch paginated endpoints. Adding a data source is pretty straightforward. You could even fork the JSON query runner source and go from there.

@dietdrpepper
Is there a solution for hosted Redash? I may be wrong, but I don’t think the query runner is accessible in hosted.

Hi @aidata I’m not sure I understand your question :confused: Please reach out to us through the in-app chat so we can look into it further.