> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/twitter.md).

# Twitter

Configure the Twitter.

## OAuth app properties

| Property                | Value                                                                                                                                                                      |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Multi-tenant**        | **Yes.** Any X user can connect through one app.                                                                                                                           |
| **Vendor review**       | **None.** You accept the Developer Agreement and describe your use case in the Developer Console.                                                                          |
| **Review time**         | Not applicable.                                                                                                                                                            |
| **Users before review** | No limit.                                                                                                                                                                  |
| **App owner**           | An X account with prepaid API credits. X bills every request made by every connected user to the app owner's account (pay-per-use, no free tier).                          |
| **Regions**             | One app works worldwide.                                                                                                                                                   |
| **Client secret**       | No expiry documented. The Developer Console shows it only once, so save it when you generate it.                                                                           |
| **Rate limits**         | Per app: 10,000 posts per 24 hours (`POST /2/tweets`). Per user: 100 posts per 15 minutes. Pay-per-use plans are capped at 3 million Post reads per monthly billing cycle. |
| **Checked**             | 2026-11-13                                                                                                                                                                 |

**Limitations**

* When the credits run out or the spending limit is reached, X blocks all requests of the app, so every connected account stops working until you add credits or the next billing cycle starts.
* Each request costs money: for example $0.015 per post created, $0.200 per post with a URL, $0.005 per post read and $0.010 per user read. Reads of the same resource are deduplicated within one UTC day.
* The access token is valid for 2 hours. The connector requests `offline.access` to get a refresh token; X does not document how long the refresh token lasts.

Sources: [Pricing](https://docs.x.com/x-api/getting-started/pricing), [Getting access](https://docs.x.com/x-api/getting-started/getting-access), [OAuth 2.0 authorization code flow](https://docs.x.com/resources/fundamentals/authentication/oauth-2-0/authorization-code), [Rate limits](https://docs.x.com/x-api/fundamentals/rate-limits). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

### Access the Twitter App Console

* Navigate to the [Twitter Developer Platform](https://developer.twitter.com/en) and sign up if you haven't already.
* You might be required to apply for a developer account where you'll need to provide some information about your intended use of Twitter’s API.

### Create OAuth app

* After logging in to your Twitter Developer account, navigate to the [Developer Dashboard](https://developer.twitter.com/en/portal/dashboard).
* Twitter should automatically create a default project and application for you. If it doesn't, click "Create Project" and follow the prompts to set up a new one. After creating the project, you'll be able to create an application. Navigate to your project and select "Add App."
* Update application details, such as the name, description, and icon, by clicking the "Edit" button. Next, configure the authentication settings.

<figure><img src="https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-54612ab9d313b1df67db786e4fc165f6b63c08cd%2Ftwitter-1.png?alt=media" alt=""><figcaption></figcaption></figure>

### User Authentication Settings

* Set the "App permissions" to "Read and write" and "Type of App" to "Web App"
* Set the Redirect URI to `https://[YOUR_API_BASE]/auth/twitter/callback`, for example `https://api.appmixer.com/auth/titter/callback`

<figure><img src="https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-18d5f24c9f8d3880ec495b125ee6ef6a94bd65a5%2Ftwitter-2.png?alt=media" alt=""><figcaption></figcaption></figure>

### Keys and Tokens

* Get the `Client Id` and `Client Secret` from the Keys and Tokens page

<figure><img src="https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-6b181120acdc20ec3820c3b290bd654fc615538b%2Ftwitter-3.png?alt=media" alt=""><figcaption></figcaption></figure>

## Backoffice configuration

Configuration ID: `appmixer:twitter` (Backoffice → Configuration; see [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how a configuration is created and how its keys reach the connector).

* `clientId` — Client ID from the **Keys and Tokens** page of the X app. Not needed when X is authenticated through the Appmixer Auth Hub.
* `clientSecret` — Client Secret from the same page. Not needed with the Auth Hub.

The same keys can be set with the CLI (`-u` updates the existing configuration instead of creating it):

```bash
appmixer service-config set appmixer:twitter -u -d '{
  "clientId": "<client id>",
  "clientSecret": "<client secret>"
}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/twitter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
