# How Does Twitter API Pagination Work?

Canonical: https://www.twitterapis.com/answers/how-does-twitter-api-pagination-work
Description: Twitter API pagination uses cursors: read next_cursor and has_more, then loop. On TwitterAPIs each page is one call at $0.0008 under a 600 req/min ceiling.
Generated: 2026-09-14T03:00:38.116Z

---

1.  [Home](/)
2.  / [Answers](/answers)
3.  / How does Twitter API pagination work?

# How does Twitter API pagination work?

Last updated July 25, 2026

Twitter API pagination works with cursors. Each response returns a page of results plus a next\_cursor token and a has\_more flag. You leave the cursor empty on the first request, feed next\_cursor back on every following request, and stop once has\_more turns false. On TwitterAPIs each page is one call at $0.0008, so paging a 1,000-record list runs about 15 to 20 calls.

Every rate here is the pricing TwitterAPIs publishes. The billed rate is $0.0008 per call; $0.04 per 1,000 tweets is derived from it at a full 20-tweet page, which is the default page size rather than a guaranteed yield (source: [twitterapis.com/pricing](/pricing)).

## What cursor pagination means

A cursor is a pointer to your place in a result set. Instead of asking for page five by number, you hand back the token the last response gave you, and the API returns the next slice. This survives new items being added mid-scroll, which numbered pages do not, so nothing is skipped or repeated between requests.

## The next\_cursor and has\_more loop

Every TwitterAPIs list response carries two fields: next\_cursor, the token for the following page, and has\_more, a boolean. Leave the cursor parameter empty on the first call, copy next\_cursor into it on each subsequent call, and keep looping while has\_more stays true. When has\_more turns false the list is complete.

## Which endpoints paginate

The follower graph and timeline endpoints page this way: user/followers and followers\_v2, user/following and following\_v2, verified\_followers, plus user tweets and likes. Each uses the identical cursor mechanic, so one loop written once works across all of them, and no state is pinned on the server between calls.

## Page size and cost

Follower endpoints return about 70 records on the first page and fewer after that, and the count parameter is currently ignored, so page size is fixed. Because every page is one flat call at $0.0008, cost scales with the number of pages, not a subscription: a 1,000-record export is roughly $0.012 to $0.016. Every page of that export bills at the same $0.0008 a call, per our pricing page.

## Cursor pagination versus numbered pages

Aspect

Cursor pagination

Numbered pages

Position marker

Opaque next\_cursor token

Page number

Handles new items

Yes, no skips or repeats

No, results can shift

Stop signal

has\_more turns false

An empty page returned

On TwitterAPIs

$0.0008 per page

Not used

> In order to perform pagination we must supply a page/cursor parameter with each of our requests.

Tweepy Cursor Tutorial. [Source](https://docs.tweepy.org/en/v3.5.0/cursor_tutorial.html)

## Questions and answers

What is a cursor in the Twitter API?

A cursor is an opaque token that marks your position in a result set. Each response returns a next\_cursor value, and passing it back on the next request returns the following page. It replaces numbered pages and keeps a scroll consistent when new items are added mid-read.

How do I get the next page of results?

Copy the next\_cursor token from the current response into the cursor parameter of your next request. On the first request leave cursor empty to land on page one. Repeat while the has\_more flag stays true, and stop when it turns false. Each page is one call at $0.0008.

How do I know when pagination is finished?

Watch the has\_more flag. Every TwitterAPIs list response returns it alongside next\_cursor. While has\_more is true there are more pages to fetch, and once it turns false you have the complete list and can stop looping. No end-of-list guesswork is needed.

How many records come back per page?

Follower endpoints return about 70 records on the first page and fewer on later pages, and the count parameter is currently ignored, so page size is fixed. Because each page is a single flat call at $0.0008, a 1,000-record list is roughly 15 to 20 calls, about $0.012 to $0.016.

Do all endpoints use the same pagination?

The follower graph and timeline endpoints share one mechanic: user/followers, following, verified\_followers, and their v2 variants, plus user tweets and likes. Because the cursor loop is identical across them, one function written once pages every endpoint, with no server-side state between calls.

Is cursor pagination better than page numbers?

For a live feed, yes. Numbered pages can skip or repeat records when new items arrive between requests. A cursor points at a fixed spot in the stream, so nothing is missed or duplicated. It is the model the Twitter API and TwitterAPIs both use.

## Keep reading

-   [Twitter Followers API](/twitter-followers-api?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-how-does-twitter-api-pagination-work)
-   [Twitter Timeline API](/twitter-timeline-api?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-how-does-twitter-api-pagination-work)
-   [Twitter API rate limits](/twitter-api-rate-limits?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-how-does-twitter-api-pagination-work)
-   [REST API documentation](https://docs.twitterapis.com/docs)
-   [Pay-per-call pricing](/pricing?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-how-does-twitter-api-pagination-work)
-   [How do you search tweets by date?](/answers/how-to-search-tweets-by-date?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-how-does-twitter-api-pagination-work)
-   [Cursor pagination worked end to end: pulling a tweet's full retweeter list](/blogs/get-all-tweet-retweeters-api-2026?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-how-does-twitter-api-pagination-work)
-   [How do you get the accounts a user follows?](/answers/how-to-get-who-a-twitter-account-follows?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-how-does-twitter-api-pagination-work)
-   [Which Twitter API publishes comparable rate limits?](/answers/twitter-api-rate-limits-in-a-comparable-unit?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-how-does-twitter-api-pagination-work)

### Start with $0.50 in free credits

No credit card. Roughly 12,500 tweets to test every endpoint.

[Get your API key](/signup?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-how-does-twitter-api-pagination-work)[See pricing](/twitter-followers-api?utm_source=aio&utm_medium=organic&utm_campaign=aeo-answers-how-does-twitter-api-pagination-work)

[

TwitterAPIs ](/)

The cheapest pay-as-you-go Twitter and X API. $0.0008 per call, which works out to $0.04 per 1,000 tweets on a full 20-tweet page. No subscriptions and no developer account.

## Product / API

-   [Pricing](/pricing)
-   [Cost Calculator](/twitter-api-cost-calculator)
-   [Rate Limits](/twitter-api-rate-limits)
-   [MCP Server](/mcp)
-   [Integrations](/integrations)
-   [Language Clients](/sdk)
-   [Changelog](/changelog)
-   [Status](/status)

## Developers

-   [Documentation](https://docs.twitterapis.com)
-   [API Reference](https://docs.twitterapis.com/docs/reference/search/tweet-advanced-search)
-   [User Info](https://docs.twitterapis.com/docs/reference/user-reads/user-info)
-   [User Tweets](https://docs.twitterapis.com/docs/reference/user-reads/user-tweets)
-   [Advanced Search](https://docs.twitterapis.com/docs/reference/search/tweet-advanced-search)
-   [Verified Followers](https://docs.twitterapis.com/docs/reference/follower-graph/user-verified-followers)

## Resources / Compare

-   [Answers](/answers)
-   [Reviews](/reviews)
-   [Free Tools](/tools)
-   [Twitter ID Finder](/tools/twitter-id-finder)
-   [Get a Twitter API Key](/twitter-api-key)
-   [Official X API Comparison](/twitter-api-pricing)
-   [Twitter API Use Cases](/twitter-api-usecases)
-   [Twitter API Alternatives](/twitter-api-alternatives)
-   [Twitter Unofficial API](/twitter-unofficial-api)
-   [Twitter Free API](/twitter-free-api)
-   [TwitterAPIs vs twitterapi.io](/twitterapis-vs-twitterapi-io)
-   [TwitterAPIs vs GetXAPI](/twitterapis-vs-getxapi)
-   [TwitterAPIs vs TweetAPI](/twitterapis-vs-tweetapi)
-   [TwitterAPIs vs TwexAPI](/twitterapis-vs-twexapi)
-   [TwitterAPIs vs RapidAPI](/twitterapis-vs-rapidapi)

## Legal

-   [About](/about)
-   [Security](/security)
-   [Trust](/privacy-and-data-handling)
-   [Terms of Service](/terms-of-service)
-   [Affiliates](/affiliates)
-   [Contact](/contact)
-   [Jobs](/jobs)

© 2026 TwitterAPIs. All rights reserved.

TwitterAPIs is an independent third-party API for developers and researchers. Not affiliated with, endorsed by, or sponsored by X Corp.

All systems operational