Pagination

How cursor-based pagination works for search, timelines, followers and other list endpoints.

List endpoints return one page at a time, with two fields:

Field	Meaning
has_next_page	true if there are more results.
next_cursor	Pass this as the cursor parameter to get the next page.

Leave cursor empty (or omit it) for the first page. Stop when has_next_page is false, next_cursor is empty, or next_cursor is the same as the cursor you just sent (a page that returns nothing new).

Python

import requests

def search_all(query, key, max_pages=10):
    url = "https://api.twitterapi.io/twitter/tweet/advanced_search"
    cursor, tweets = "", []
    for _ in range(max_pages):
        r = requests.get(url, headers={"x-api-key": key},
                         params={"query": query, "queryType": "Latest", "cursor": cursor}, timeout=30)
        r.raise_for_status()
        data = r.json()
        tweets += data.get("tweets", [])
        nxt = data.get("next_cursor")
        if not data.get("has_next_page") or not nxt or nxt == cursor:
            break
        cursor = nxt
    return tweets

Notes

• Each page is billed as its own request. See Pricing.
• Page sizes differ by endpoint: search and timelines return up to 20 tweets; followers / followings up to 200 users; follower IDs up to 5,000 IDs.
• Set a max_pages limit in your code so a bug can’t page forever.
• On some endpoints X can report more results when there are none; you then get an empty page, often with the same cursor back. The stop rule above handles this.
• For “new tweets since last time”, searching with a time window (for example since_time: / until_time: in the query) is usually cheaper than paging deep.