#1

Hi, accordingly to the documentation [1] I understand the response to list the direct messages [2], the next_cursor is only present when the number of direct messages returned is larger than 50. But in my case, I see the number of DM is only 9 and the next_cursor field is set to a non null value. As the next_cursor is set, my program perform a second request to retrieve the DM, wasting api count limits, as there are no pagination. Is this a know issue ?

  1. GET direct_messages/events/list | Docs | Twitter Developer Platform
  2. twurl -X GET /1.1/direct_messages/events/list.json

Thanks

Claudio

#2

I noticed for subsequent requests, if there is no new DM it returns the same next_cursor. If there is a new DM, the next_cursor changes.

#3

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.