From 8aee913c0585b2fb875181b81f82c68621539ee3 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Tue, 9 Jun 2026 23:41:36 +0000 Subject: [PATCH] docs: enforce sentence case, second person, and fix typos across prose pages --- developer-guidelines.mdx | 36 +++++++++---------- developer-terms.mdx | 2 +- .../account-activity/introduction.mdx | 2 +- enterprise-api/activity/introduction.mdx | 18 +++++----- enterprise-api/activity/quickstart.mdx | 16 ++++----- enterprise-api/webhooks/quickstart.mdx | 2 +- fundamentals/authentication/basic-auth.mdx | 2 +- fundamentals/authentication/faq.mdx | 2 +- .../authentication/oauth-1-0a/oauth-echo.mdx | 2 +- .../authentication/oauth-1-0a/overview.mdx | 4 +-- .../oauth-1-0a/pin-based-oauth.mdx | 2 +- .../oauth-2-0/application-only.mdx | 4 +-- .../oauth-2-0/bearer-tokens.mdx | 2 +- important-resources.mdx | 16 ++++----- livestreams.mdx | 2 +- overview.mdx | 10 +++--- support.mdx | 30 ++++++++-------- tools-and-libraries.mdx | 6 ++-- x-ads-api/introduction.mdx | 4 +-- x-api/fundamentals/data-dictionary.mdx | 2 +- 20 files changed, 82 insertions(+), 82 deletions(-) diff --git a/developer-guidelines.mdx b/developer-guidelines.mdx index 8cc461c86..b9a2eb252 100644 --- a/developer-guidelines.mdx +++ b/developer-guidelines.mdx @@ -31,22 +31,22 @@ icon: "scale-balanced" Before building, ask yourself these questions. If you answer **"no"** to any of them, your app likely violates X's policies. - + For interactions, did the user **explicitly request** it? Is your app's purpose and behavior **clear to users**? (Automated accounts must be labeled.) - + Can users **easily opt out** of any ongoing interactions? - + Does it provide **real value** beyond self-promotion? - + Are you **only using the official API** (not scraping/browser automation)? - + Are you **within rate limits** and respecting usage policies? @@ -62,7 +62,7 @@ Before building, ask yourself these questions. If you answer **"no"** to any of Real-world examples to help you understand what's permitted. **These rules apply to all apps**—whether you're building a bot, mobile app, web integration, browser extension, analytics dashboard, or any other tool that uses the X API. - + | Scenario | Allowed? | Why | |----------|:--------:|-----| | Automated account posts scheduled content (news, weather, quotes) | | Informational, no unsolicited mentions | @@ -74,7 +74,7 @@ Real-world examples to help you understand what's permitted. **These rules apply | App posts to trending topics to gain visibility | | Trend manipulation | | Multiple city-specific alert accounts (e.g., @WeatherNYC, @WeatherLA) | | Allowed—non-duplicative, location-specific content | - + | Scenario | Allowed? | Why | |----------|:--------:|-----| | App responds to @mentions asking for help | | User-initiated request | @@ -107,7 +107,7 @@ Real-world examples to help you understand what's permitted. **These rules apply **Likes must be directly initiated by the authenticated user.** Automated, bulk, or indiscriminate liking — including auto-liking by keyword, hashtag, user, or schedule — is prohibited. Apps may not offer "auto-like" features or sell likes as a service. This applies to all apps—bots, mobile apps, browser extensions, or any integration. - + | Scenario | Allowed? | Why | |----------|:--------:|-----| | App sends product recommendations when asked | | User-initiated | @@ -116,7 +116,7 @@ Real-world examples to help you understand what's permitted. **These rules apply | Service selling likes/follows/retweets | | Strictly prohibited | | Tip service that sends crypto when user requests | | User-initiated—comply with financial regulations. [Conditions apply](#gray-areas-explained) | - + | Scenario | Allowed? | Why | |----------|:--------:|-----| | App tracks brand mentions for analytics dashboard | | Valid use case | @@ -209,7 +209,7 @@ All automated accounts using the X API must meet these requirements: Many developers have questions about edge cases. Here's guidance on common gray areas. - + **Allowed if:** - User explicitly requests it (e.g., DMs asking for a recommendation) @@ -225,7 +225,7 @@ Many developers have questions about edge cases. Here's guidance on common gray - + - **Requires prior approval from X** before deployment - Must still follow all rules (no unsolicited mentions, properly labeled) - Contact X via the [Policy Support form](https://help.x.com/forms/platform) before launching @@ -234,7 +234,7 @@ Many developers have questions about edge cases. Here's guidance on common gray Deploying AI-generated replies without approval is a violation, even if the content itself is helpful. - + **Not allowed** as automated DMs—this counts as unsolicited contact, even though they followed you. **Alternatives:** @@ -243,7 +243,7 @@ Many developers have questions about edge cases. Here's guidance on common gray - Auto-reply only if they DM you first - + **Allowed if:** - Each account serves **non-duplicative** purposes (e.g., @EarthquakeJP, @EarthquakeCA) @@ -258,7 +258,7 @@ Many developers have questions about edge cases. Here's guidance on common gray - + **Allowed if:** - User initiates (mentions you, DMs you, or explicitly opts in) @@ -274,7 +274,7 @@ Many developers have questions about edge cases. Here's guidance on common gray - + **Proceed with caution:** - Requiring follows/retweets as entry can be seen as engagement manipulation - Must comply with [X's contest guidelines](https://help.x.com/en/rules-and-policies/x-contest-rules) @@ -391,14 +391,14 @@ You must delete X Content from your systems when requested: Your obligations as a developer: - + - Use **industry-standard security** practices to protect X data - Never share your API credentials or tokens - Store credentials securely (environment variables, secret managers—not in code) - Implement proper authentication in your apps - + If you experience a security breach involving X data: - **Notify X immediately** - Take steps to mitigate the breach @@ -411,7 +411,7 @@ Your obligations as a developer: - Don't use confidential info for competitive purposes - + - X may audit your compliance **up to once per year** - You must provide reasonable access and documentation - Keep records of how you use X data diff --git a/developer-terms.mdx b/developer-terms.mdx index 367c9280b..de98cfe13 100644 --- a/developer-terms.mdx +++ b/developer-terms.mdx @@ -11,7 +11,7 @@ import { Button } from '/snippets/button.mdx'; ## Overview -Developer use of X materials and content is subject to and governed by our Developer Policy and agreements. +Our Developer Policy and agreements govern your use of X materials and content.
-### Spaces Events +### Spaces events Spaces events are triggered when a user starts or ends a Space. @@ -61,7 +61,7 @@ Spaces events are triggered when a user starts or ends a Space. | `spaces.start` | Fired when a user starts a Space | `user_id` | | `spaces.end` | Fired when a user ends a Space | `user_id` | -### Post Events +### Post events Post events are triggered when a user creates or deletes a Post. @@ -76,7 +76,7 @@ Post events are triggered when a user creates or deletes a Post. If you want targeted keyword filtering, boolean logic, geo targeting, language filters, or any of the other operators that the Filtered Stream supports, use the [Filtered Stream](/x-api/posts/filtered-stream/introduction) endpoint instead. -### Legacy DM Events +### Legacy DM events Legacy DM events pertain to the legacy, unencrypted DM system. @@ -87,7 +87,7 @@ Legacy DM events pertain to the legacy, unencrypted DM system. | `dm.read` | Fired when a user reads the filtered users unencrypted DM message, or "read receipt" | `user_id` | | `dm.indicate_typing` | Fired when a user is typing a message to the filtered user | `user_id` | -### Chat Events +### Chat events Chat events pertain to the new, encrypted messaging stack, or XChat. @@ -98,7 +98,7 @@ Chat events pertain to the new, encrypted messaging stack, or XChat. | `chat.conversation_join` | Fired when a user joins an encrypted chat conversation | `user_id` | -### News Events +### News events News events provide updates on trending topics and headlines curated by Grok. @@ -116,7 +116,7 @@ In future releases, XAA will expand to support additional event types including The X Activity API distinguishes between **public events** and **private events** as at parity with the X app as explained below. -### Public Events +### Public events Public events are activities that a public user account performs publicly that are visible to all X users. These events are visible to all users on the X platform and don't require OAuth authentication from the user in order to view. @@ -126,7 +126,7 @@ Public events are activities that a public user account performs publicly that a For these public events, you can create subscriptions by specifying the user ID in your filter and receive them via XAA. -### Private Events +### Private events Private events are activities that require explicit user consent through OAuth authentication. A User has to authenticate via X and give explicit permission to a developer app to access these events. diff --git a/enterprise-api/activity/quickstart.mdx b/enterprise-api/activity/quickstart.mdx index 98cd7f1e8..03c13ccf6 100644 --- a/enterprise-api/activity/quickstart.mdx +++ b/enterprise-api/activity/quickstart.mdx @@ -7,10 +7,10 @@ description: "This guide explains how to subscribe for and receive events using import { Button } from '/snippets/button.mdx'; -This guide explains how to subscribe for and receive events using the X Activity API endpoints. There generally 3 steps involved: -1. Identify the User ID for the User who's events you want to filter on -2. Create a subscription for the type of event you want to filter for that User -3. Receive the events using webhook or persistent http stream connection +This guide explains how to subscribe for and receive events using the X Activity API endpoints. There are generally three steps: +1. Identify the user ID for the user whose events you want to filter on. +2. Create a subscription for the type of event you want to filter for that user. +3. Receive the events using a webhook or persistent HTTP stream connection. **Prerequisites** @@ -139,7 +139,7 @@ When Xdevelopers account updates their profile bio, the event will be delivered The X Activity API provides endpoints to manage your subscriptions through standard CRUD operations. -### Create Subscription +### Create subscription Create a new subscription to receive events: @@ -180,7 +180,7 @@ curl -H "Authorization: Bearer YOUR_BEARER_TOKEN" \ } ``` -### List Subscriptions +### List subscriptions Retrieve all active subscriptions for your application: @@ -219,7 +219,7 @@ curl -H "Authorization: Bearer YOUR_BEARER_TOKEN" \ } ``` -### Delete Subscription +### Delete subscription Remove a subscription: @@ -244,7 +244,7 @@ curl -H "Authorization: Bearer YOUR_BEARER_TOKEN" \ `total_subscriptions` shows the remaining number of subscriptions associated with your app after the delete operation. -### Update Subscription +### Update subscription The PUT endpoint allows you to update a subscription's delivery method or tag. diff --git a/enterprise-api/webhooks/quickstart.mdx b/enterprise-api/webhooks/quickstart.mdx index 833642bd6..61eb9313e 100644 --- a/enterprise-api/webhooks/quickstart.mdx +++ b/enterprise-api/webhooks/quickstart.mdx @@ -161,7 +161,7 @@ def webhook(): X's webhook-based APIs provide two methods for confirming the security of your webhook server: -### Challenge-Response Check (CRC) +### Challenge-response check (CRC) The CRC enables X to confirm ownership of the web app receiving webhook events. See [Step 2](#2-the-crc-check) above for full implementation details. diff --git a/fundamentals/authentication/basic-auth.mdx b/fundamentals/authentication/basic-auth.mdx index fd48b21d0..0dd2aaf65 100644 --- a/fundamentals/authentication/basic-auth.mdx +++ b/fundamentals/authentication/basic-auth.mdx @@ -12,7 +12,7 @@ Many of X's enterprise APIs require the use of HTTP Basic Authentication. To mak When building a request using Basic Authentication, make sure you add the Authentication: Basic HTTP header with encoded credentials over HTTPS. -In the following cURL request example, you would replace `` and `` with your credentiails before sending the request: +In the following cURL request example, you would replace `` and `` with your credentials before sending the request: ```bash curl -v --compressed -u: diff --git a/fundamentals/authentication/faq.mdx b/fundamentals/authentication/faq.mdx index 3b407b6a4..86575c577 100644 --- a/fundamentals/authentication/faq.mdx +++ b/fundamentals/authentication/faq.mdx @@ -24,7 +24,7 @@ description: Answers to common questions about OAuth 1.0a, OAuth 2.0, access tok ## Technical - Access tokens are not explicitly expired. An access token will be invalidated if a user explicitly revokes an application in the their X account settings, or if X suspends an application. If an application is suspended, there will be a note in the [X app](/resources/fundamentals/developer-apps) dashboard stating that it has been suspended. + Access tokens are not explicitly expired. An access token will be invalidated if a user explicitly revokes an application in their X account settings, or if X suspends an application. If an application is suspended, there will be a note in the [X app](/resources/fundamentals/developer-apps) dashboard stating that it has been suspended. Assume a user’s access token _may_ become invalid at any time. If this happens, prompt the user to re-authorize the application. Ensuring that this situation is handled gracefully is important for a good user experience. diff --git a/fundamentals/authentication/oauth-1-0a/oauth-echo.mdx b/fundamentals/authentication/oauth-1-0a/oauth-echo.mdx index a63d40d14..e47311176 100644 --- a/fundamentals/authentication/oauth-1-0a/oauth-echo.mdx +++ b/fundamentals/authentication/oauth-1-0a/oauth-echo.mdx @@ -32,7 +32,7 @@ Keep in mind that the entire transaction period needs to occur within an amount Alternatively, instead of sending these two parameters in the header, they could be sent in the POST as x\_auth\_service_provider and x\_verify\_credentials_authorization — in this case, remember to escape and include the parameters in the OAuth signature base string — similar to encoding parameters in any request. It’s best to use HTTP headers to keep the operations as separate as possible. -The Delegators goal, at this point, is to verify that the User is who they say they are before it saves the media. Once the Delegator receives all the data above via its upload method, it should temporarily store the image, and then construct a call to the endpoint specified in the x-auth-service-provider header — in this case, https://api.x.com/1.1/account/verify_credentials.json, using the same OAuth authentication header provided by the Consumer in the x-verify-credentials-authorization header. +The Delegator's goal, at this point, is to verify that the User is who they say they are before it saves the media. Once the Delegator receives all the data above via its upload method, it should temporarily store the image, and then construct a call to the endpoint specified in the x-auth-service-provider header — in this case, https://api.x.com/1.1/account/verify_credentials.json, using the same OAuth authentication header provided by the Consumer in the x-verify-credentials-authorization header.   #### OAuth Echo best practices diff --git a/fundamentals/authentication/oauth-1-0a/overview.mdx b/fundamentals/authentication/oauth-1-0a/overview.mdx index 8068d47c3..e0f086dbb 100644 --- a/fundamentals/authentication/oauth-1-0a/overview.mdx +++ b/fundamentals/authentication/oauth-1-0a/overview.mdx @@ -23,7 +23,7 @@ You have to sign each API request by passing several generated keys and tokens i | | | | :--- | :--- | | API key and secret:

`oauth_consumer_key`

`oauth_consumer_secret` | Think of these as the user name and password that represents your X developer app when making API requests. | -| Access token and secret:

`oauth_token`

`oauth_token_secret` | An access token and access token secret are user-specific credentials used to authenticate OAuth 1.0a API requests. They specify the X account the request is made on behalf of.

You can generate your own access token and token secret if you would like your app to make requests on behalf of the same X account associated with your developer account on the [X developer app's]/resources/fundamentals/developer-apps) details page.

If you'd like to generate access tokens for a different user, see "Making requests on behalf of users" below. | +| Access token and secret:

`oauth_token`

`oauth_token_secret` | An access token and access token secret are user-specific credentials used to authenticate OAuth 1.0a API requests. They specify the X account the request is made on behalf of.

You can generate your own access token and token secret if you would like your app to make requests on behalf of the same X account associated with your developer account on the [X developer app's](/resources/fundamentals/developer-apps) details page.

If you'd like to generate access tokens for a different user, see "Making requests on behalf of users" below. | #### Making requests on behalf of users @@ -31,7 +31,7 @@ When creating a signature, you need a set of access tokens that represent the us You can generate a set of access tokens that represents the X account that owns the X developer app from the [app’s details page,](https://developer.x.com/content/developer-twitter/en/apps) but if you are wanting to make a request on behalf of a different X account, that account’s owner must grant access to you by signing in to their account as part of the [3-legged OAuth flow](/resources/fundamentals/authentication#obtaining-access-tokens-using-3-legged-oauth-flow). The output of this process is a set of access tokens (oauth\_token and oauth\_token_secret) that can be used to make an OAuth 1.0a request. -Once you have these keys and tokens, you can either [create a signature](/resources/fundamentals/authentication#creating-a-signature) from scratch. We don't recommended this unless you know what you are doing, or if you're using one of the tools mentioned below to make a request to an endpoint that requires OAuth 1.0a. +Once you have these keys and tokens, you can either [create a signature](/resources/fundamentals/authentication#creating-a-signature) from scratch. We don't recommend this unless you know what you're doing, or if you're using one of the tools mentioned below to make a request to an endpoint that requires OAuth 1.0a. For reference, here is an example of a signed cURL request with all of the generated tokens passed in an authorization header: diff --git a/fundamentals/authentication/oauth-1-0a/pin-based-oauth.mdx b/fundamentals/authentication/oauth-1-0a/pin-based-oauth.mdx index 65b899bce..3cbcabae0 100644 --- a/fundamentals/authentication/oauth-1-0a/pin-based-oauth.mdx +++ b/fundamentals/authentication/oauth-1-0a/pin-based-oauth.mdx @@ -25,7 +25,7 @@ The PIN-based flow is implemented in the same way as [3-legged authorization](/r 1. The value for `oauth_callback` must be set to `oob` during the [POST oauth/request_token](/resources/fundamentals/authentication/api-reference#post-oauth-request-token) call. -2. After the user is sent to X to authorize your app using either a [GET oauth/authenticate](/resources/fundamentals/authentication/api-reference#get-oauth-authenticate) or [GET oauth/authorize URL](/resources/fundamentals/authentication/api-reference#get-oauth-authorize), they will not be redirected to your `callback_url`, instead they will see a screen with a X generated ~7 digit PIN with directions to enter the PIN into your applications name. +2. After the user is sent to X to authorize your app using either a [GET oauth/authenticate](/resources/fundamentals/authentication/api-reference#get-oauth-authenticate) or [GET oauth/authorize URL](/resources/fundamentals/authentication/api-reference#get-oauth-authorize), they aren't redirected to your `callback_url`. Instead, they see a screen with an X-generated ~7-digit PIN, along with directions to enter the PIN into your application. 3. The user enters this PIN into your application, and your application uses the PIN number as the `oauth_verifier` in the [POST oauth/access_token](/resources/fundamentals/authentication/api-reference#post-oauth-access-token) to obtain an access_token. diff --git a/fundamentals/authentication/oauth-2-0/application-only.mdx b/fundamentals/authentication/oauth-2-0/application-only.mdx index babc0613b..23667536f 100644 --- a/fundamentals/authentication/oauth-2-0/application-only.mdx +++ b/fundamentals/authentication/oauth-2-0/application-only.mdx @@ -31,7 +31,7 @@ Please note that only [OAuth 1.0a](/resources/fundamentals/authentication/oauth * Retrieve user's email addresses -#### Auth Flow +#### Auth flow To use this method, you need to use a [App only Access Token](/resources/fundamentals/authentication/oauth-2-0/application-only)(also known as [Bearer Token](/resources/fundamentals/authentication/oauth-2-0/bearer-tokens)). You can generate an App only Access Token (Bearer Token) by passing your consumer key and secret through the [POST oauth2/token](/resources/fundamentals/authentication/api-reference#post-oauth2-token) endpoint.  @@ -209,7 +209,7 @@ Content-Length: 61 ``` #### App only Access Token (Bearer Token) used on endpoint which doesn't support application-only auth -Requesting an endpoint which requires a user context (such as `statuses/home_timeline`) with a n App only Access Token (Bearer Token) will produce: +Requesting an endpoint which requires a user context (such as `statuses/home_timeline`) with an App-only Access Token (Bearer Token) will produce: ```json HTTP/1.1 403 Forbidden Content-Type: application/json; charset=utf-8 diff --git a/fundamentals/authentication/oauth-2-0/bearer-tokens.mdx b/fundamentals/authentication/oauth-2-0/bearer-tokens.mdx index 1dd09fa1e..c156cebf5 100644 --- a/fundamentals/authentication/oauth-2-0/bearer-tokens.mdx +++ b/fundamentals/authentication/oauth-2-0/bearer-tokens.mdx @@ -26,7 +26,7 @@ The products that require the use of a Bearer Token are as follows: You will need to [sign up for a developer account](https://developer.x.com/en/portal/petition/essential/basic-info) and to have created a [X App](/resources/fundamentals/developer-apps). Once you have those, you'll also need to obtain the API keys found in the [Developer Console](/resources/fundamentals/developer-portal). Follow the steps below: -1. Login to your X account on developer.x.com. +1. Log in to your X account on developer.x.com. 2. Navigate to the [X App dashboard](https://developer.x.com/content/developer-twitter/en/apps) and open the X App for which you would like to generate access tokens. 3. Navigate to the "keys and tokens" page. 4. You'll find the API keys, user Access Tokens, and Bearer Token on this page. diff --git a/important-resources.mdx b/important-resources.mdx index 0fd71914c..f40476aa8 100644 --- a/important-resources.mdx +++ b/important-resources.mdx @@ -13,16 +13,16 @@ Bookmark these essential resources for X API development. ## Documentation - + Complete endpoint documentation with parameters and examples. - + Object schemas for posts, users, media, and more. OAuth 1.0a and OAuth 2.0 implementation guides. - + Per-endpoint limits and best practices. @@ -47,13 +47,13 @@ Bookmark these essential resources for X API development. Step-by-step guides for common use cases. - + Example apps and code samples. - + Ideas and inspiration for projects. - + Upgrade from v1.1 to v2. @@ -63,10 +63,10 @@ Bookmark these essential resources for X API development. ## Community and support - + Ask questions and share solutions with the community. - + FAQs, troubleshooting, and contact options. diff --git a/livestreams.mdx b/livestreams.mdx index 0e22d312a..2d247d469 100644 --- a/livestreams.mdx +++ b/livestreams.mdx @@ -9,7 +9,7 @@ keywords: ["livestreams", "video tutorials", "developer videos", "webinars", "br import { BroadcastCarousel } from '/snippets/broadcast-carousel.mdx'; -View recordings and replays of previous broadcasts about the X Developer Platform, designed to help the developer community learn and build with our tools. +View recordings and replays of previous broadcasts about the X Developer Platform, designed to help you learn and build with our tools. These include deep dives, getting started guides, and more. diff --git a/overview.mdx b/overview.mdx index ab425687b..11b44f982 100644 --- a/overview.mdx +++ b/overview.mdx @@ -30,7 +30,7 @@ Earn free [xAI API](https://docs.x.ai) credits when you purchase X API credits ## Get started - +
Get your API keys and make your first request in minutes. - + Explore endpoints for posts, users, spaces, DMs, lists, and more. @@ -77,13 +77,13 @@ Earn free [xAI API](https://docs.x.ai) credits when you purchase X API credits Step-by-step guides for common use cases and integrations. - + Official SDKs and community libraries for every language. - + Get help from the community and X team. - + llms.txt, skill.md, MCP servers, and resources for AI-powered development. diff --git a/support.mdx b/support.mdx index c1eda2744..7a516dd21 100644 --- a/support.mdx +++ b/support.mdx @@ -13,10 +13,10 @@ Whether you're troubleshooting an issue, looking for guidance, or want to connec ## Community and help - + Ask questions, share your projects, and get help from the X developer community and team. This is the best place to get support for technical questions. - + Check the current operational status of X API v2, Enterprise APIs, and the Developer Console. @@ -26,13 +26,13 @@ Whether you're troubleshooting an issue, looking for guidance, or want to connec ## Contact and forms - + Interested in enterprise-level API access? Submit your interest and our team will reach out. - + Get help with billing questions for Self-serve and Enterprise API subscriptions. - + Questions about policies, compliance, or need approval for specific use cases? Contact our policy team. @@ -42,22 +42,22 @@ Whether you're troubleshooting an issue, looking for guidance, or want to connec ## Documentation and resources - + New to the X API? Start here to get your API keys and make your first request. - + Complete reference for all X API v2 endpoints, parameters, and response formats. - + Learn about OAuth 1.0a, OAuth 2.0, and how to authenticate your API requests. - + Official Python and TypeScript SDKs to speed up your development. - + Understand rate limits and how to handle them in your application. - + Reference for API error codes and how to resolve common issues. @@ -67,16 +67,16 @@ Whether you're troubleshooting an issue, looking for guidance, or want to connec ## Policies and guidelines - + Practical guide to what's allowed and what's not when building with the X API. - + The binding legal terms for X API access. - + Rules and expectations for building on X. - + Activities that are prohibited or require special approval. diff --git a/tools-and-libraries.mdx b/tools-and-libraries.mdx index 8d3301013..c07ad7bd1 100644 --- a/tools-and-libraries.mdx +++ b/tools-and-libraries.mdx @@ -65,16 +65,16 @@ console.log(userResponse.data?.username); ## Developer tools - + Interactive API testing for all v2 endpoints. curl-like CLI for the X API with built-in OAuth authentication. No manual token management. - + Local mock server for testing X API v2 endpoints without using real credits. - + XMCP, llms.txt, skill.md, docs MCP server, and resources for AI-powered development. diff --git a/x-ads-api/introduction.mdx b/x-ads-api/introduction.mdx index f2e417938..37f18015e 100644 --- a/x-ads-api/introduction.mdx +++ b/x-ads-api/introduction.mdx @@ -26,9 +26,9 @@ The X Ads API connects developers to X's advertising platform to build solutions If you would rather work with our endpoints using a command line tool, xurl is built for you! -## For Ads API access +## Get Ads API access -For Ads API Access, please submit a request using the [Ads API Access Form](/forms/ads-api-access). Please allow up to 3 business days for us to review and process your submission. +To request Ads API access, submit the [Ads API Access Form](/forms/ads-api-access). Allow up to 3 business days for review and processing. ## Need help? diff --git a/x-api/fundamentals/data-dictionary.mdx b/x-api/fundamentals/data-dictionary.mdx index 7445c9a3c..e184a1da8 100644 --- a/x-api/fundamentals/data-dictionary.mdx +++ b/x-api/fundamentals/data-dictionary.mdx @@ -17,7 +17,7 @@ The X API returns rich structured JSON. This dictionary documents every availabl **Full detailed field tables → [Data Dictionary Reference](/x-api/fundamentals/data-dictionary/reference)** -## Quick navigation +## Object reference | Object | Description | Fields parameter | |:-------|:------------|:-----------------|