> For the complete documentation index, see [llms.txt](https://runtimedesigns.gitbook.io/token-buzz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://runtimedesigns.gitbook.io/token-buzz/connecting-data-byok/twitter.md).

# X (Twitter)

TokenBuzz fetches X/Twitter posts through [twitterapi.io](https://twitterapi.io), a third-party API proxy. You sign up with twitterapi.io directly, get an API key, and paste it into TokenBuzz.

## What you'll need

* A twitterapi.io account with an active plan.
* Your twitterapi.io API key (a single string shown in the twitterapi.io dashboard).

## Get your credentials

1. Go to <https://twitterapi.io> and sign up or log in.
2. Open your dashboard. Your API key is displayed on the main page or under an "API Key" section.
3. Copy the key — it is a long alphanumeric string.

## Connect in TokenBuzz

1. In TokenBuzz, open **Account → API Keys**.
2. Make sure the mode selector is set to **Per-source keys**.
3. Select the **X (twitterapi.io)** tab.
4. Paste your API key into the **API key** field.
5. Click **Validate & save**. TokenBuzz calls twitterapi.io to verify the key before storing it. You'll see a confirmation card showing the last four characters of the key and the validation date.
6. Optionally enable **Use my key for background polling** to have TokenBuzz automatically refresh your watchlist tokens in the background.

To remove the key, click **Remove key** on the configured card.

## Security & notes

* Your key is encrypted with AWS KMS before being stored. Only the last four characters are ever shown in the UI.
* Keys can be rotated by removing the existing key and saving a new one.
* If twitterapi.io returns a 401 or 403, TokenBuzz marks the key as invalid and sends you an email with a link to re-enter it.
* Queries run against your twitterapi.io quota. TokenBuzz does not meter or cap your usage beyond what your twitterapi.io plan allows.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://runtimedesigns.gitbook.io/token-buzz/connecting-data-byok/twitter.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.