Skip to content

Get Twitter API key access: the steps, and how to skip them

Get Twitter API key access: the console steps X lists today, which credentials you receive, what the rules say, and the quicker route to an X data key.

Piyushh · November 13, 2026 · 3 min read

A short footbridge beside a long winding path, picturing a quicker route to an API key.

To get a Twitter API key, sign in at console.x.com with your X account, accept the Developer Agreement and Policy, create an app, and copy the credentials X shows you. X's docs call it a self-service flow, and the keys are shown only once. That is the whole route to generate a Twitter API key from X. If you only need to read data, a hosted API can get you a working key faster. I cover that at the end.

Every X step below comes from X's getting access page, checked 2026-11-13. It describes what that page says today, not how the flow worked in the past. X changes this flow, so if the console differs, follow the console.

Steps to get access to the Twitter API

  1. Sign in. Go to console.x.com, now the Twitter API portal, and sign in with your X account.
  2. Accept the terms. Review and accept the Developer Agreement and Policy, then fill in your profile with basic details on how you'll use the API.
  3. Create an app. Click New App and give it a name, a description and your use case.
  4. Save the credentials. The console generates them when it creates the app.

According to the page, you get an API Key and Secret, a Bearer Token, an Access Token and Secret, and a Client ID and Secret. Credentials are shown only once, so put them in a password manager right away.

The page mentions no manual review or waiting period. If the console asks you for anything else, go with the console.

What each credential is for

Use the Bearer Token for read-only public data. The API Key and Secret identify your app and sign OAuth 1.0a requests, while the Access Token and Secret let you act as your own account. OAuth 2.0 user-context requests need the Client ID and Secret. Our guides on Twitter API authentication and the Twitter consumer key and secret explain which one each call needs.

First call with your new key

Public reads work with a Bearer Token. This one calls X's recent search:

curl -s "https://api.x.com/2/tweets/search/recent?query=crm%20recommendation" \
  -H "Authorization: Bearer $X_BEARER_TOKEN"

A 402 or a payment error means you should check your credit balance in the console. When we checked X's pricing page on 2026-11-13, it listed pay-per-use rates such as $0.005 per post read. The details are in is the X API free.

Rules and licence to read first

Before you build, read X's Developer Agreement and Policy, which is the one you accept in step two. It covers what you may do with the data and how you must use the API. I haven't summarised its licence terms here. They are long, they can change, and my summary is no substitute for reading them. If you plan to store tweets, redistribute them or feed them into model training, read those sections first. For the use case text, see the post on how to answer the use case question.

An unofficial Twitter API, and the quicker route

"Twitter unofficial API" is the usual name for services that return X data without you holding an X key. ChatterAPI is one of them. It is independent and not affiliated with X Corp. You send one key:

curl -s "https://api.chatterapi.com/v1/x/tweets/search?q=crm%20recommendation&sort=latest" \
  -H "Authorization: Bearer $CHATTERAPI_KEY"

Back comes JSON with the tweets, their authors and their engagement, at 2 credits per page of about 20 tweets. You don't need a developer app or OAuth, and X doesn't bill you. To see the same data without any key, try the free X tweet search tool.

There are trade-offs. This is a read API, not a first-party one, so you have no contract with X, and some features, such as a push stream, aren't offered. If you need first-party terms, use X's key. If you just need to read data on a schedule and move on, this route is shorter. For the larger picture, see does Twitter have an API.

Pick one

  • If you need to post as your brand or want a first-party agreement, get X's key with the steps above.
  • If you need X data in a script, dashboard or agent, use a read API.
  • If you're not sure yet, try the free tool first and decide after.

Sign up with Google to get a key. The 7-day free trial includes 1,000 credits, which covers about 500 pages of tweet search. Plans start at $19 a month on the pricing page, and the quickstart walks you through the first call. Get started here.

FAQ

How do I get a Twitter API key?
Per X's docs, checked 2026-11-13: sign in at console.x.com, accept the Developer Agreement and Policy, complete your profile with basic API usage information, create an app, and save the credentials shown. They are displayed once.
Is there an approval process for Twitter API access?
X's getting-access page, checked 2026-11-13, describes a self-service flow and mentions no manual review. That can change, so follow the console and read what it shows you.
What is the Twitter API portal?
It is X's Developer Console at console.x.com, where you create apps, copy keys and tokens and manage billing.
Is there an unofficial Twitter API?
Yes. Independent read APIs, ChatterAPI among them, return X data without you holding an X developer key. They are not made by X. Read the terms of any provider and the X rules for your use.
Do I have to pay to use the Twitter API?
X's pricing page, checked 2026-11-13, lists pay-per-use pricing, for example $0.005 per post read. Check that page for current rates.

More on X (Twitter) API

Try it free for 7 days.

1,000 credits to make your first calls. One key for Reddit and X, over REST or MCP.