Yeah, I saw that the last cursor starts with “0|”. After my last update “next_cursor” wouldn’t be returned if you reach the end of the list.
Also, I’ve added cursor parameter to the followers list as well.
I think I found a bug with pagination: On the last page it will try to paginate to a non-existent page and return “{“following”:[],“next_cursor”:null}”.
The cursor should know about the last page - for example: 0|1683199037278257095. In case of a single page it should also start with 0.
Yeah I was looking for that. I tested it and it works fine. It would be nice to include a “count” parameter to specify and control the amount of data returned.
i have you need GET/friends/list
you can try our API https://rapidapi.com/huojiecs/api/twitter-api-v1-1-enterprise
welcome to see my
Yeah, I saw that the last cursor starts with “0|”. After my last update “next_cursor” wouldn’t be returned if you reach the end of the list.
Also, I’ve added cursor parameter to the followers list as well.
I think I found a bug with pagination: On the last page it will try to paginate to a non-existent page and return “{“following”:[],“next_cursor”:null}”.
The cursor should know about the last page - for example: 0|1683199037278257095. In case of a single page it should also start with 0.
I hope that makes sense. 😃
Yeah I was looking for that. I tested it and it works fine. It would be nice to include a “count” parameter to specify and control the amount of data returned.
Hello,
Yes, sure, today I’ve added optional parameter “cursor” to this API. Also I’ve added a “next_cursor” value to every response.
To get the next page you should pass the “next_cursor” value to the “cursor” parameter.
I hope thats is what you’re looking for 😃 I’m going to add this cursor optional paramters to other endpoints in a few days.
Sincerely yours,
Aleksandr