Documentation Index
Fetch the complete documentation index at: https://docs.x.com/llms.txt
Use this file to discover all available pages before exploring further.
Enterprise compared to X API v2
Similarities- Granularity
- Pagination
- Timezone
- Endpoint URLs
- App and Project requirement
- Available time periods
- Response data format
- HTTP methods
- Request time formats
- Request parameters
- Filtering operators
Similarities
Granularity While the parameter for selecting granularity of the returned data is different (bucket for the enterprise version, granularity for the v2 version), the values that you can pass with that parameter are the same, as well as the default behavior:
dayhour(default)minute
since_id and until_id), both enterprise and v2 allow you to paginate using time (fromDate and toDate with enterprise, and start_time and end_time for v2).
If you are using the enterprise version, you will use the next parameter to paginate, the next token field will be called next, and it will be located at the root in the response.
If you are using v2, you can use either the next_token or pagination_token parameter to paginate, and your next token will be located at meta.next_token in the response.
Timezone
As noted in the pagination section, you can navigate different pages of data using time for both enterprise and v2. In both cases, you will be using UTC as the timezone when using these parameters.
Differences
Endpoint URLs- Enterprise endpoints:
- 30 day -
http://gnip-api.x.com/search/30day/accounts/:account_name/:label/counts.json - Full-archive -
http://gnip-api.x.com/search/fullarchive/accounts/:account_name/:label/counts.json
- 30 day -
- X API v2 endpoints *