Hey @jje!
This looks to be possible using relay-based cursor pagination. You can set your REST resource to have a blank base URL allowing you to pass the entire link generated by your API as the URL for your query. I've used a generic RESTQuery resource here that has authentication tokens passed to its headers:
Here the rel="next"
and rel="previous"
links are parsed into the Previous cursor
and Next cursor
fields respectively. Since table.afterCursor
and table.beforeCursor
are alternately defined based on whether you're paginating forward or backward passing {{table.beforeCursor || table.afterCursor || defaultUrl}}
to your table will select the correct URL each time.
Does that work?
Edit: The code for this was done only using limit
as an extra parameter of the default query but you can build out the base URL to include as many additional parameters as you'd like.