# HTTP 400: Pagination token expired or invalid

- **ID:** `api/rest-api-pagination-token-expired`
- **Domain:** api
- **Category:** request_error
- **Verification:** ai_generated
- **Fix Rate:** 88%

## Root Cause

The pagination cursor or token used in the API request has expired or was generated for a different query context, causing the server to reject it.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| REST API v3.0 | active | — | — |
| cursor-based pagination | active | — | — |
| Twitter API v2 | active | — | — |

## Workarounds

1. **Restart pagination from the beginning by omitting the cursor parameter.** (90% success)
   ```
   Restart pagination from the beginning by omitting the cursor parameter.
   ```
2. **Cache the initial request and re-fetch from scratch if token expires.** (85% success)
   ```
   Cache the initial request and re-fetch from scratch if token expires.
   ```

## Dead Ends

- **** — The token is already expired; waiting will not revive it. (90% fail)
- **** — Tokens are opaque and server-generated; manual modification breaks integrity checks. (95% fail)
- **** — Some APIs do not support offset pagination; this may not be an option. (60% fail)