canonical: https://jentic.com/apis/twitter.com/twitter-api

# Twitter API

twitter.com/legacy version 1.1. The API exposes 83 endpoints.

## For AI agents

Programmatically account.settings.post, account.settings.get. Covers 83 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- account.settings.post
- account.settings.get
- account.update_delivery_device
- account.update_profile
- accounts.update_profile_background_image
- accounts.update_profile_colors
- accounts.update_profile_image

## Use cases

### Developer Tools Operations

Use the Twitter API to perform developer tools operations programmatically. The API provides 83 endpoints covering core functionality including account.settings.post, account.settings.get, account.update_delivery_device.

Example prompt: Call POST /account/settings.json to account.settings.post

### Automated Account Management

Automate account operations by combining multiple Twitter API endpoints. Agents can account.settings.get and then account.update_delivery_device in a single workflow.

Example prompt: Call GET /account/settings.json to account.settings.get, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Twitter API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'account.settings.post', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /account/settings.json | account.settings.post |
| GET | /account/settings.json | account.settings.get |
| POST | /account/update_delivery_device.json | account.update_delivery_device |
| POST | /account/update_profile.json | account.update_profile |
| POST | /account/update_profile_background_image.json | accounts.update_profile_background_image |
| POST | /account/update_profile_colors.json | accounts.update_profile_colors |
| POST | /account/update_profile_image.json | accounts.update_profile_image |
| GET | /application/rate_limit_status.json | application.rate_limit_status |

## Key resources

- **Account** — Operations for account
- **Application** — Operations for application
- **Blocks** — Operations for blocks
- **Direct_Messages** — Operations for direct_messages
- **Direct_Messages.Json** — Operations for direct_messages.json

## Why Jentic

- **Setup:** Wiring the legacy Twitter API by hand means pointing at the 1.1 host, matching each account and application operation to the right form-encoded fields, and handling its rate-limit windows yourself. Through Jentic you install once, import the Twitter API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** This Twitter API passes its account and profile targets through the request body, so scope your agent to the operations it needs, such as reading account settings or checking rate-limit status. You choose the operations it may call, so a write like updating the profile or delivery device is not included unless you add it.
- **Credential handling:** Your Twitter credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'read account settings' or 'check the rate-limit status', and Jentic returns the matching Twitter API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Twitter API use?

The Twitter API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I account.settings.post with the Twitter API?

Yes. Use the POST /account/settings.json endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Twitter API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I account.settings.post through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'account.settings.post'. Jentic returns the matching Twitter API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Twitter API have?

The Twitter API exposes 83 endpoints covering account, application, blocks operations.

### Can I limit what my agent is allowed to do with the Twitter API?

Yes. Because Jentic One is self-hosted, you set the rules for which Twitter API operations your agent may call and which credential it uses. You can scope the agent to read-only work like getting account settings or checking rate-limit status, and leave out writes such as updating the profile or the delivery device unless you add them. The agent can only run the operations you have granted.