It looks like you’re running into an issue where using start_cursor set to the previous response’s end_cursor returns the same set of results, so you’re stuck on the same page. Based on the Pipedream REST API documentation, the paginated response includes start_cursor and end_cursor, but does not mention a next_cursor. The docs do not specify exactly how to paginate, but the typical convention is: - To get the next page, you pass a parameter like start_cursor or after with the value of the previous response’s end_cursor. However, if using start_cursor=<end_cursor> returns the same data, this could be: 1. An API bug or undocumented behavior 2. A misunderstanding of the correct pagination parameter ### What to try - Double-check the API docs or any examples for the correct pagination parameter. Sometimes APIs use after, cursor, or other names. - Try incrementing the cursor manually (if it’s a number or offset), but in your case, it looks like a token, so this is unlikely to work. - If you continue to get the same results, this may be a bug or a limitation in the API. ### What to do next Since the Pipedream REST API documentation does not provide more detail, and your experience suggests the documented approach is not working, I recommend reaching out to Pipedream support for clarification or to report a potential bug. You can contact them directly at: Support - Pipedream Sorry for the trouble—this is likely something only the Pipedream team can resolve or clarify.