Next_cursor in Threads API pagination gets very long

Hello everyone!

I am having an issue with the next_cursor value that is being returned from the Threads API. The issue is that the next_cursor gets so long that it reaches a point where is not longer accepted by the page_token parameter in the Threads API. As such, pagination does not work after a specific page.

I’d share the cursor but lat time I tried, my post marked as spam…
This is not the issue with the Emails API, cursors there are fairly small.

Do you have any ideas on how to fix this and make pagination work on threads?

Thanks

Hello @gpapidas you’re previous post was flagged as SPAM by a user, I marked it as secure, so let’s continue on that one and I will close this one…

1 Like