> ## Documentation Index
> Fetch the complete documentation index at: https://x-preview-mintlify-22943c32.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Filtered stream migration overview
> Migrate filtered stream consumers from Standard v1.1 or PowerTrack to X API v2 by mapping endpoints, operators, rules, and authentication requirements.
## Comparing X API's filtered stream endpoints
The v2 filtered stream endpoints group is replacing the [standard v1.1 statuses/filter](https://developer.x.com/en/docs/x-api/v1/tweets/filter-realtime/api-reference/post-statuses-filter) and [PowerTrack API](/x-api/enterprise-gnip-2.0/powertrack-api). If you have code, apps, or tools that use an older version of the filtered stream endpoint, and are considering migrating to the newer X API v2 endpoint, then this comparison can help you get started.
See our more in depth migration guides for:
[Migrating from Standard v1.1 compared to X API v2](x-api/posts/filtered-stream#standard-v1-1-compared-to-x-api-v2)
[Migrating from PowerTrack API migration to X API v2](/x-api/enterprise-gnip-2.0/powertrack-api#powertrack-operators)
The following table compares the filtered streaming endpoints X offers:
| **Description** | **Standard v1.1** | **PowerTrack API** | **X API v2** |
| :------------------------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Access | X App | Requires an enterprise contract and account | Requires a developer account ([sign up](https://developer.x.com/en/portal/petition/essential/basic-info)), and [X App](/resources/fundamentals/developer-apps) within a [Project](/resources/fundamentals/developer-apps) |
| :--- | :--- | :--- | :--- |
| Host domain | **[https://stream.x.com](https://stream.x.com)** | **[https://gnip-stream.x.com](https://gnip-stream.x.com)** | **[https://api.x.com](https://api.x.com)** |
| Endpoint path | **1.1/statuses/filter.json** | **/stream/powertrack/accounts/{gnip_account_name}/publishers/twitter/{stream_label}.json**
**/rules/powertrack/accounts/{gnip_account_name}/publishers/twitter/{stream_label}.json **
**/rules/powertrack/accounts/{gnip_account_name}/publishers/twitter/{stream_label}/validation.json** | **/2/tweets/search/stream**
**/2/tweets/search/stream/rules** |
| [Authentication](/resources/fundamentals/authentication) | OAuth 1.0a User Context | HTTP Basic Authentication | OAuth 2.0 App-Only |
| HTTP methods supported | POST | GET
POST | GET
POST |
| Required parameters | Rule defined on connection as parameter, at least one of:
\* **follow**
\* **track**
\* **locations** | No required parameters for streaming connection, optional backfill parameter.
Rules managed separately | No required parameters for streaming connection, optional parameters to define response format and add [backfill recovery feature](/x-api/fundamentals/recovery-and-redundancy) for Academic Research access.
Rules managed separately |
| Delivery type | Streaming | Streaming
REST (for rules management) | Streaming
REST (for rules management) |
| Default request rate limits | 5 connection attempts per 5 min | 60 requests per min aggregated for both POST and GET requests
/rules: 60 requests per minute, aggregated across all requests to /rules endpoint for the specific stream's API (POST and GET). | Depends on the endpoint. See [rate limits](/x-api/fundamentals/rate-limits) for current limits. |
| Maximum allowed connections | 2 concurrent per authorized user | Supports multiple/redundant connections, determined by contract | Pay-per-use: 1 |
| [Recovery and redundancy features](/x-api/fundamentals/recovery-and-redundancy) | None | Backfill, redundant connections, and the Replay API | |
| Keep-alive signal/heartbeats | blank lines (\r\n or similar) at least every 20 seconds | blank lines (\r\n or similar) every 10 seconds | blank lines (\r\n or similar) at least every 20 seconds |
| Latency | 10 seconds | 2 seconds
At least 10 seconds for URL unwinding enrichment | 10 seconds |
| Maximum allowed rules | 1 rule (within the endpoint connection request) | Determined by contract up to 250,000 | Pay-per-use: 1,000 rules |
| Rule filter limitations | One query per connection, up to either:
- 400 track keywords
- 5000 follow user IDs
- 25 location boxes | Up to 2,048 characters per rule | Pay-per-use: 1,024 characters per rule |
| [Post JSON format](/x-api/fundamentals/data-dictionary) | Standard v1.1 format | [Native Enriched](/x-api/enterprise-gnip-2.0/fundamentals/data-dictionary#native-enriched-tweet-object) or Activity Streams (selected within the [console](/x-api/enterprise-gnip-2.0/fundamentals/overview)) | [X API v2 format](/x-api/fundamentals/data-dictionary) (determined by **fields** and **expansions** request parameters, not backward-compatible with v1.1 formats)
To learn more about how to migrate from the Standard v1.1 format to the X API v2 format, please visit our [data formats migration guide](/x-api/migrate/data-format-migration). We will be releasing additional data format migration guides for Native Enriched and Activity Streams soon. |
| Provides Post edit history and metadata | ✔ | ✔ | ✔ |
| Unique Features | Filtering done via query parameters on connection request
No configuration UI | Filtering done via rules created through an independent endpoint
[Enrichment](/x-api/enterprise-gnip-2.0/enterprise-gnip#enrichments) features available in contract
Configuration on console.gnip.com UI | Filtering done via [rules](/x-api/posts/filtered-stream/integrate/build-a-rule) created through an independent endpoint
[Metrics](/x-api/fundamentals/metrics) and URL enrichment features included
Object [fields](/x-api/fundamentals/fields) and [expansions](/x-api/fundamentals/expansions) specified with request parameters
Post [Annotations](/x-api/fundamentals/post-annotations)
[Conversation ID](/x-api/fundamentals/conversation-id) operator and field
Configuration through [Developer Console](/resources/fundamentals/developer-portal) |