claycurry · mintlify · Apr 27, 2026
diff --git a/changelog.mdx b/changelog.mdx
@@ -557,7 +557,7 @@ Today we announced [Early Access to the first endpoints of the new X API](https:
 
   * [Filtered stream](/x-api/posts/filtered-stream)
 
-  * [Sampled stream](/x-api/posts/sample-stream)
+  * [Sampled stream](/x-api/posts/volume-streams/introduction)
 
   You can find a full list of the new functionality available, and find migration resources on our \[X API v2: Early Access docs page]https://developer.x.com/en/docs/x-api/early-access).
 

diff --git a/enterprise/customer-directory.mdx b/enterprise/customer-directory.mdx
@@ -10,7 +10,7 @@ import { LogoCard } from '/snippets/logo_card.mdx';
 
 Our enterprise data customers receive commercial-level access to APIs and dedicated account and developer support. Apply for enterprise API access to get the highest level of access and reliability.
 
-[Apply for enterprise access →](/resources/enterprise/forms/enterprise-api-interest)
+[Apply for enterprise access →](/forms/enterprise-api-interest)
 
 ## X Official Partners
 

diff --git a/fundamentals/authentication/guides/v2-authentication-mapping.mdx b/fundamentals/authentication/guides/v2-authentication-mapping.mdx
diff --git a/overview.mdx b/overview.mdx
@@ -61,7 +61,7 @@ Build, analyze, and innovate with X's real-time global data. Access posts, users
   <Card title="X Ads API" icon="rectangle-ad" href="/x-ads-api/introduction">
     Programmatically manage ad campaigns, targeting, creatives, and analytics.
   </Card>
-  <Card title="X for Websites" icon="laptop-code" href="/x-for-websites/x-for-websites">
+  <Card title="X for Websites" icon="laptop-code" href="/x-for-websites/overview">
     Embed posts, timelines, and follow buttons on your website.
   </Card>
 </CardGroup>

diff --git a/tutorials/explore-a-users-posts.mdx b/tutorials/explore-a-users-posts.mdx
@@ -151,6 +151,6 @@ Once you have an understanding of how to navigate a user’s Posts, you can also
 ## Resources
 
 *   Learn more about the [user Tweet timeline and the user mention timeline endpoints](/x-api/posts/timelines/introduction).
-*   Check out the [API reference for the user Tweet timeline endpoint](/x-api/posts/user-posts-timeline-by-user-id) to learn more about what’s available.
-*   Check out the [API reference for the user mention timeline endpoint](/x-api/posts/user-mention-timeline-by-user-id) to learn more about what’s available.
+*   Check out the [API reference for the user Tweet timeline endpoint](/x-api/users/get-posts) to learn more about what’s available.
+*   Check out the [API reference for the user mention timeline endpoint](/x-api/users/get-mentions) to learn more about what’s available.
 *   Get inspired by reading our other [tutorials](/tutorials).
diff --git a/tutorials/postman-getting-started.mdx b/tutorials/postman-getting-started.mdx
@@ -18,7 +18,7 @@ We currently have two Postman collections available:
 
 ### Prerequisites
 
-Before you get started with using Xs Postman collections, you will need to make sure you have the proper access and credentials for the X developer platform tool of your choosing. You can learn more about getting access via our [“Getting started” page](/resources/platform-overview). 
+Before you get started with using Xs Postman collections, you will need to make sure you have the proper access and credentials for the X developer platform tool of your choosing. You can learn more about getting access via our [“Getting started” page](/overview). 
 
 Once you have a [developer account,](https://developer.x.com/en/portal/petition/essential/basic-info) have set up a [developer App](/resources/fundamentals/developer-apps) and have a set of [authentication](/resources/fundamentals/authentication) keys and tokens, and have properly set up your environment to make requests to the specific API that you plan to use, you can follow the below steps to get started.
 

diff --git a/x-api/account-activity/introduction.mdx b/x-api/account-activity/introduction.mdx
@@ -64,7 +64,7 @@ You will receive all related activities below for each user subscription on your
 - **Subscription revokes** (by user)
 
 <Note>
-We do not deliver home timeline data via the Account Activity API. Use the [User Posts timeline by User ID](/x-api/posts/timelines/get-user-tweets) endpoint to pull this data.
+We do not deliver home timeline data via the Account Activity API. Use the [User Posts timeline by User ID](/x-api/users/get-posts) endpoint to pull this data.
 
 The returned Posts from the Account Activity API count towards the monthly [Post cap](/x-api/fundamentals/post-cap).
 </Note>

diff --git a/x-api/activity/introduction.mdx b/x-api/activity/introduction.mdx
@@ -154,7 +154,7 @@ The X Activity API has different subscription limits based on your account tier:
 To access these endpoints, you will need:
 
 * An approved [developer account](https://developer.x.com/en/portal/petition/essential/basic-info).
-* To authenticate using the keys and tokens from a [developer App](/resources/fundamentals/developer-apps) that is located within a [Project](/resources/fundamentals/projects). 
+* To authenticate using the keys and tokens from a [developer App](/resources/fundamentals/developer-apps) that is located within a [Project](/fundamentals/developer-portal). 
 
 Learn more about getting access to the X API v2 endpoints in our [getting started guide](/x-api/getting-started/getting-access).
 </Note>

diff --git a/x-api/communities/lookup/introduction.mdx b/x-api/communities/lookup/introduction.mdx
@@ -69,7 +69,7 @@ community.fields=name,description,member_count,created_at" \
   <Card title="Search Communities" icon="magnifying-glass" href="/x-api/communities/search/introduction">
     Find Communities by keyword
   </Card>
-  <Card title="API Reference" icon="code" href="/x-api/communities/community-lookup">
+  <Card title="API Reference" icon="code" href="/x-api/communities/get-community-by-id">
     Full endpoint documentation
   </Card>
 </CardGroup>
diff --git a/x-api/compliance/batch-compliance/introduction.mdx b/x-api/compliance/batch-compliance/introduction.mdx
@@ -110,7 +110,7 @@ curl -X POST "https://api.x.com/2/compliance/jobs" \
   <Card title="Integration guide" icon="book" href="/x-api/compliance/batch-compliance/integrate">
     Key concepts and best practices
   </Card>
-  <Card title="API Reference" icon="code" href="/x-api/compliance/create-job">
+  <Card title="API Reference" icon="code" href="/x-api/compliance/create-compliance-job">
     Full endpoint documentation
   </Card>
 </CardGroup>
diff --git a/x-api/compliance/batch-compliance/quickstart.mdx b/x-api/compliance/batch-compliance/quickstart.mdx
@@ -183,7 +183,7 @@ curl "https://api.x.com/2/compliance/jobs?type=tweets" \
   <Card title="Compliance streams" icon="stream" href="/x-api/compliance/streams/introduction">
     Real-time compliance events
   </Card>
-  <Card title="API Reference" icon="code" href="/x-api/compliance/create-job">
+  <Card title="API Reference" icon="code" href="/x-api/compliance/create-compliance-job">
     Full endpoint documentation
   </Card>
 </CardGroup>
diff --git a/x-api/direct-messages/lookup/quickstart.mdx b/x-api/direct-messages/lookup/quickstart.mdx
@@ -340,7 +340,7 @@ for await (const page of paginator) {
   <Card title="Integration guide" icon="book" href="/x-api/direct-messages/lookup/integrate">
     Key concepts and best practices
   </Card>
-  <Card title="API Reference" icon="code" href="/x-api/direct-messages/returns-dm-events">
+  <Card title="API Reference" icon="code" href="/x-api/direct-messages/get-dm-events">
     Full endpoint documentation
   </Card>
 </CardGroup>
diff --git a/x-api/direct-messages/manage/introduction.mdx b/x-api/direct-messages/manage/introduction.mdx
@@ -96,7 +96,7 @@ You can send text messages and attach media:
   <Card title="DM lookup" icon="messages" href="/x-api/direct-messages/lookup/introduction">
     Retrieve DM events
   </Card>
-  <Card title="API Reference" icon="code" href="/x-api/direct-messages/send-new-message">
+  <Card title="API Reference" icon="code" href="/x-api/direct-messages/create-dm-message-by-conversation-id">
     Full endpoint documentation
   </Card>
 </CardGroup>
diff --git a/x-api/fundamentals/response-codes-and-errors.mdx b/x-api/fundamentals/response-codes-and-errors.mdx
@@ -161,7 +161,7 @@ This happens when requesting multiple resources and some are unavailable.
 - Check for full-buffer disconnects (client not consuming fast enough)
 - Verify at least one stream rule exists
 
-[Streaming guide →](/x-api/posts/filtered-stream/integrate/handling-disconnections)
+[Streaming guide →](/x-api/fundamentals/handling-disconnections)
 </Accordion>
 
 ---

diff --git a/x-api/lists/list-lookup/integrate.mdx b/x-api/lists/list-lookup/integrate.mdx
@@ -63,7 +63,7 @@ console.log(response.data);
 
 | Method | Endpoint | Description |
 |:-------|:---------|:------------|
-| GET | [`/2/lists/:id`](/x-api/lists/get-list) | Get List by ID |
+| GET | [`/2/lists/:id`](/x-api/lists/get-list-by-id) | Get List by ID |
 | GET | [`/2/users/:id/owned_lists`](/x-api/users/get-owned-lists) | Get Lists owned by a user |
 
 ---
@@ -272,7 +272,7 @@ console.log(`Found ${lists.length} lists`);
   <Card title="List Posts" icon="list" href="/x-api/lists/list-tweets/introduction">
     Get Posts from a List
   </Card>
-  <Card title="API Reference" icon="code" href="/x-api/lists/get-list">
+  <Card title="API Reference" icon="code" href="/x-api/lists/get-list-by-id">
     Full endpoint documentation
   </Card>
   <Card title="Sample code" icon="github" href="https://github.com/xdevplatform/Twitter-API-v2-sample-code">

diff --git a/x-api/lists/list-members/introduction.mdx b/x-api/lists/list-members/introduction.mdx
@@ -85,7 +85,7 @@ curl -X POST "https://api.x.com/2/lists/1234567890/members" \
   <Card title="Integration guide" icon="book" href="/x-api/lists/list-members/integrate">
     Key concepts and best practices
   </Card>
-  <Card title="API Reference" icon="code" href="/x-api/lists/list-members-lookup">
+  <Card title="API Reference" icon="code" href="/x-api/lists/get-list-members">
     Full endpoint documentation
   </Card>
 </CardGroup>
diff --git a/x-api/lists/list-tweets/introduction.mdx b/x-api/lists/list-tweets/introduction.mdx
@@ -63,7 +63,7 @@ max_results=100" \
   <Card title="List lookup" icon="list" href="/x-api/lists/list-lookup/introduction">
     Get List details
   </Card>
-  <Card title="API Reference" icon="code" href="/x-api/lists/list-tweets-lookup">
+  <Card title="API Reference" icon="code" href="/x-api/lists/get-list-posts">
     Full endpoint documentation
   </Card>
 </CardGroup>
diff --git a/x-api/lists/list-tweets/quickstart.mdx b/x-api/lists/list-tweets/quickstart.mdx
@@ -148,7 +148,7 @@ This endpoint returns up to 800 of the most recent Posts from the List.
   <Card title="Integration guide" icon="book" href="/x-api/lists/list-tweets/integrate">
     Key concepts and best practices
   </Card>
-  <Card title="API Reference" icon="code" href="/x-api/lists/get-list-tweets">
+  <Card title="API Reference" icon="code" href="/x-api/lists/get-list-posts">
     Full endpoint documentation
   </Card>
 </CardGroup>
diff --git a/x-api/lists/pinned-lists/introduction.mdx b/x-api/lists/pinned-lists/introduction.mdx
@@ -74,7 +74,7 @@ curl -X POST "https://api.x.com/2/users/123456789/pinned_lists" \
   <Card title="Integration guide" icon="book" href="/x-api/lists/pinned-lists/integrate">
     Key concepts and best practices
   </Card>
-  <Card title="API Reference" icon="code" href="/x-api/lists/pinned-lists-lookup">
+  <Card title="API Reference" icon="code" href="/x-api/users/get-pinned-lists">
     Full endpoint documentation
   </Card>
 </CardGroup>
diff --git a/x-api/lists/pinned-lists/quickstart/pinned-list-lookup.mdx b/x-api/lists/pinned-lists/quickstart/pinned-list-lookup.mdx
@@ -130,7 +130,7 @@ response.data?.forEach((lst) => {
   <Card title="List lookup" icon="list" href="/x-api/lists/list-lookup/quickstart">
     Get List details
   </Card>
-  <Card title="API Reference" icon="code" href="/x-api/lists/get-users-pinned-lists">
+  <Card title="API Reference" icon="code" href="/x-api/users/get-pinned-lists">
     Full endpoint documentation
   </Card>
 </CardGroup>
diff --git a/x-api/media/introduction.mdx b/x-api/media/introduction.mdx
@@ -20,7 +20,7 @@ Objects such as Posts, Direct Messages, user profile pictures, hosted Ads cards,
 
 An entity which contains media object(s) can be created by following these steps:
 
-1. Upload the media file(s) using either the recommended [chunked](/x-api-/media/quickstart/media-upload-chunked) upload (images/GIF/video), or the older [simple](/x-api/media-upload/media-upload) upload (images only).
+1. Upload the media file(s) using either the recommended [chunked](/x-api/media/quickstart/media-upload-chunked) upload (images/GIF/video), or the older [simple](/x-api/media/upload-media) upload (images only).
 1. Receive a `media_id` from step 1. This step may be repeated multiple times with different media if the entity allows multiple `media_id` parameters to be passed in.
 1. Create the entity by calling the appropriate endpoint, including the `media_id` and other required parameters. For example, attach a `media_id` to a Post using the [`POST /2/tweets`](/x-api/posts/creation-of-a-post) endpoint.
 

diff --git a/x-api/media/quickstart/best-practices.mdx b/x-api/media/quickstart/best-practices.mdx
@@ -4,7 +4,7 @@ sidebarTitle: Best practices
 keywords: ["media upload best practices", "upload media", "media best practices", "image upload", "video upload", "media upload guide"]
 ---
 
-There are a few important concepts to understand when using the [`POST /2/media/upload`](/x-api/media/media-upload) endpoint. Uploading media with OAuth can be a bit tricky, so we’ve outlined some things to keep in mind as well as a working sample of how to use this endpoint here.
+There are a few important concepts to understand when using the [`POST /2/media/upload`](/x-api/media/upload-media) endpoint. Uploading media with OAuth can be a bit tricky, so we’ve outlined some things to keep in mind as well as a working sample of how to use this endpoint here.
 
 ## Keep in mind
 

diff --git a/x-api/media/quickstart/media-upload-chunked.mdx b/x-api/media/quickstart/media-upload-chunked.mdx
@@ -354,7 +354,7 @@ console.log(`Posted: ${response.data?.id}`);
   <Card title="Create Posts" icon="message" href="/x-api/posts/manage-tweets/quickstart">
     Post with media
   </Card>
-  <Card title="API Reference" icon="code" href="/x-api/media/media-upload-init">
+  <Card title="API Reference" icon="code" href="/x-api/media/initialize-media-upload">
     Full endpoint documentation
   </Card>
 </CardGroup>
diff --git a/x-api/migrate/overview.mdx b/x-api/migrate/overview.mdx
@@ -53,7 +53,7 @@ Some of the improvements to the API include:
 - [Access to new metrics](/x-api/fundamentals/metrics)
 - [Easily identify and filter for conversations that belong to a reply thread](/x-api/fundamentals/conversation-id)
 - [Advanced functionality and increased access to data for academic researchers](https://developer.x.com/content/developer-twitter/en/products/twitter-api/academic-research)
-- [Recovery and redundancy functionality for streaming endpoints](/x-api/posts/filtered-stream/integrate/recovery-and-redundancy-features)
+- [Recovery and redundancy functionality for streaming endpoints](/x-api/fundamentals/recovery-and-redundancy)
 - [Easily return counts of Tweets that match a query](/x-api/posts/counts/introduction)
 - [Support for Edit Tweets](/x-api/fundamentals/edit-posts)
 - High confidence spam filtering
@@ -137,7 +137,7 @@ A new Tweet field helps identify which conversation thread a Tweet belongs to. A
 In order to use v2 endpoints, you will need the following things:
 
 - [A developer account](https://developer.x.com/en/portal/petition/essential/basic-info)
-- [A developer App](https://developer.x.com/en/apps) created within a [Project](resources/fundamentals/projects)
+- [A developer App](https://developer.x.com/en/apps) created within a [Project](/fundamentals/developer-portal)
 - [Keys and tokens](resources/fundamentals/authentication) from that Project’s developer App
 
 Please note the importance of using keys and tokens from an App within an App. If you are using keys and tokens from an App outside of a Project, you will not be able to make a request to v2 endpoints.