Name: Twitter API: Search Tweets, Users, Followers and Trends
Brand: twitterapi-io
SKU: api-twitterapi-io-twitter-x-data
Availability: InStock
Author: API Market

# Twitter X Data API

## Overview

The Twitter X Data API gives read-only access to public Twitter/X data over plain REST, run by TwitterAPI.io. Eleven GET endpoints cover tweet search with X search operators, a user's latest tweets, replies and quote tweets, mentions, user profiles and the About panel, followers and followings, follow relationship checks and trends by location. List endpoints use cursor pagination: send the `next_cursor` of one page as `cursor` to get the next. You do not need an X developer account or X API keys.

It is built for brand monitoring and social listening tools, research datasets, influencer analysis, engagement tracking and AI agents that need to look up tweets and accounts. In our tests a search for `from:NASA` returned NASA's newest tweets with like, reply and view counts, the profile call returned NASA's 92 million followers, the follow check confirmed that @elonmusk follows @NASA, and worldwide trends came back ranked. The service is not affiliated with or endorsed by X Corp.

## Features

*   **11 endpoints**: search, timelines, replies, quotes, mentions, profiles, about, followers, followings, follow check and trends.
*   **X search operators**: `from:`, `to:`, `since:`, `until:`, `lang:`, `min_faves:`, `filter:media` and more.
*   **Cursor pagination**: `has_next_page` and `next_cursor` on every list.
*   **Read only**: no posting, liking, following or messages.
*   **Usage-based billing**: units per call depend on how much data is returned, and failed calls are free.

## Use Cases

*   **Brand monitoring**: run a search on a schedule and store new tweets.
*   **Social listening and research**: collect tweets for a topic or a time window.
*   **Influencer analysis**: profiles, followers and recent tweets for a list of accounts.
*   **Engagement tracking**: replies and quote tweets on your own posts.
*   **AI agents**: give an assistant a read-only tool for tweets, users and trends.

## API Documentation

### Base URL

All requests use the following base URL.

```
https://prod.api.market/api/v1/twitterapi-io/twitter-x-data
```

### Authentication

All requests are authenticated with the `x-api-market-key` header.

```
x-api-market-key: YOUR_API_KEY
```

Replace `YOUR_API_KEY` with your actual API key.

### Endpoints

#### 1. Search tweets

Returns up to 20 tweets per page that match a query, with full X search operator support.

**Method:** `GET`

**Endpoint:** `/twitter/tweet/advanced_search`

**Parameters:**

| Name | In | Description | Type | Required | Default | Max Value |
|---|---|---|---|---|---|---|
| `query` | query | Search query with X operators, for example `from:NASA`, `since:2026-11-01`, `lang:en`, `min_faves:100` | string | Yes | - | - |
| `queryType` | query | `Latest` or `Top` | string | Yes | `Latest` | - |
| `cursor` | query | `next_cursor` from the previous page | string | No | - | - |

**Example Request:**

```bash
curl -X GET 'https://prod.api.market/api/v1/twitterapi-io/twitter-x-data/twitter/tweet/advanced_search?query=from%3ANASA&queryType=Latest' \
  -H 'x-api-market-key: YOUR_API_KEY'
```

**Example Response (200 OK):**

```json
{
  "tweets": [
    {
      "type": "tweet",
      "id": "2121364270281822467",
      "url": "https://x.com/NASA/status/2121364270281822467",
      "text": "RT @NASASpox: From MAX POWER to Mars, it was a week to remember at @NASA!\n\n🇺🇸 MAX POWER takes over @NASAKennedy\n🌕 New Moon Base awards\n✈️ X…",
      "retweetCount": 21,
      "replyCount": 9,
      "likeCount": 179,
      "quoteCount": 1,
      "viewCount": 94155,
      "createdAt": "Fri Nov 13 22:07:09 +0000 2026",
      "lang": "en",
      "isReply": false,
      "conversationId": "2121364270281822467",
      "author": {
        "userName": "NASA",
        "name": "NASA",
        "followers": 92245641,
        "isBlueVerified": true
      }
    }
  ],
  "has_next_page": true,
  "next_cursor": "CURSOR"
}
```

The tweet above is shortened to its main fields. Every tweet also carries `entities`, `bookmarkCount`, `inReplyToId` and the full `author` object.

#### 2. Get a user's latest tweets

Returns a user's newest tweets, up to 20 per page, by `userName` or `userId`.

**Method:** `GET`

**Endpoint:** `/twitter/user/last_tweets`

**Parameters:**

| Name | In | Description | Type | Required | Default | Max Value |
|---|---|---|---|---|---|---|
| `userName` | query | Screen name without @, for example `NASA` | string | Yes, or `userId` | - | - |
| `userId` | query | Numeric user id | string | No | - | - |
| `includeReplies` | query | Also return the user's replies | boolean | No | false | - |
| `cursor` | query | `next_cursor` from the previous page | string | No | - | - |

**Example Request:**

```bash
curl -X GET 'https://prod.api.market/api/v1/twitterapi-io/twitter-x-data/twitter/user/last_tweets?userName=NASA' \
  -H 'x-api-market-key: YOUR_API_KEY'
```

**Example Response (200 OK):**

```json
{
  "status": "success",
  "code": 0,
  "msg": "success",
  "data": {
    "pin_tweet": null,
    "tweets": [
      {
        "id": "2121364270281822467",
        "text": "RT @NASASpox: From MAX POWER to Mars, it was a week to remember at @NASA!\n\n🇺🇸 MAX POWER takes over @NASAKennedy\n🌕 New Moon Base awards\n✈️ X…",
        "replyCount": 9,
        "likeCount": 179,
        "viewCount": 94271,
        "createdAt": "Fri Nov 13 22:07:09 +0000 2026"
      }
    ]
  },
  "has_next_page": true,
  "next_cursor": "CURSOR"
}
```

Tweets have the same fields as in Search tweets.

#### 3. Get tweet replies

Returns replies to a tweet, optionally inside a time window.

**Method:** `GET`

**Endpoint:** `/twitter/tweet/replies`

**Parameters:**

| Name | In | Description | Type | Required | Default | Max Value |
|---|---|---|---|---|---|---|
| `tweetId` | query | Id of the tweet | string | Yes | - | - |
| `sinceTime` | query | Only replies after this Unix time (seconds) | integer | No | - | - |
| `untilTime` | query | Only replies before this Unix time (seconds) | integer | No | - | - |
| `cursor` | query | `next_cursor` from the previous page | string | No | - | - |

**Example Request:**

```bash
curl -X GET 'https://prod.api.market/api/v1/twitterapi-io/twitter-x-data/twitter/tweet/replies?tweetId=2121364270281822467' \
  -H 'x-api-market-key: YOUR_API_KEY'
```

**Example Response (200 OK):**

```json
{
  "tweets": [],
  "has_next_page": false,
  "next_cursor": null,
  "status": "success",
  "msg": "success"
}
```

A tweet with no replies yet returns an empty `tweets` list, as above.

#### 4. Get tweet quotes

Returns quote tweets of a tweet, up to 20 per page.

**Method:** `GET`

**Endpoint:** `/twitter/tweet/quotes`

**Parameters:**

| Name | In | Description | Type | Required | Default | Max Value |
|---|---|---|---|---|---|---|
| `tweetId` | query | Id of the tweet | string | Yes | - | - |
| `sinceTime` | query | Only quotes after this Unix time (seconds) | integer | No | - | - |
| `untilTime` | query | Only quotes before this Unix time (seconds) | integer | No | - | - |
| `includeReplies` | query | Include quote tweets that are replies | boolean | No | true | - |
| `cursor` | query | `next_cursor` from the previous page | string | No | - | - |

**Example Request:**

```bash
curl -X GET 'https://prod.api.market/api/v1/twitterapi-io/twitter-x-data/twitter/tweet/quotes?tweetId=2121364270281822467' \
  -H 'x-api-market-key: YOUR_API_KEY'
```

**Example Response (200 OK):**

```json
{
  "tweets": [],
  "has_next_page": false,
  "next_cursor": "",
  "status": "success",
  "msg": "success"
}
```

#### 5. Get user mentions

Returns tweets that mention a user, optionally inside a time window.

**Method:** `GET`

**Endpoint:** `/twitter/user/mentions`

**Parameters:**

| Name | In | Description | Type | Required | Default | Max Value |
|---|---|---|---|---|---|---|
| `userName` | query | Screen name without @ | string | Yes | - | - |
| `sinceTime` | query | Only tweets after this Unix time (seconds) | integer | No | - | - |
| `untilTime` | query | Only tweets before this Unix time (seconds) | integer | No | - | - |
| `cursor` | query | `next_cursor` from the previous page | string | No | - | - |

**Example Request:**

```bash
curl -X GET 'https://prod.api.market/api/v1/twitterapi-io/twitter-x-data/twitter/user/mentions?userName=NASA' \
  -H 'x-api-market-key: YOUR_API_KEY'
```

**Example Response (200 OK):**

```json
{
  "tweets": [
    {
      "id": "2121393984085840192",
      "text": "@NASASolarSystem @NASAJPL @NASA To think I was 1 year old when Voyager 1 launched 🥹",
      "replyCount": 0,
      "likeCount": 0,
      "viewCount": 4,
      "createdAt": "Sat Nov 14 00:05:14 +0000 2026"
    }
  ],
  "has_next_page": true,
  "next_cursor": "CURSOR",
  "status": "success",
  "msg": "success"
}
```

#### 6. Get user profile

Returns one user's profile: name, bio, follower and following counts, created date and verification flags.

**Method:** `GET`

**Endpoint:** `/twitter/user/info`

**Parameters:**

| Name | In | Description | Type | Required | Default | Max Value |
|---|---|---|---|---|---|---|
| `userName` | query | Screen name without @ | string | Yes | - | - |

**Example Request:**

```bash
curl -X GET 'https://prod.api.market/api/v1/twitterapi-io/twitter-x-data/twitter/user/info?userName=NASA' \
  -H 'x-api-market-key: YOUR_API_KEY'
```

**Example Response (200 OK):**

```json
{
  "status": "success",
  "msg": "success",
  "data": {
    "id": "11348282",
    "name": "NASA",
    "userName": "NASA",
    "location": "Pale Blue Dot",
    "url": "https://t.co/9NkQJKAnuU",
    "description": "Making the seemingly impossible, possible. ✨",
    "entities": {
      "description": {},
      "url": {
        "urls": [
          {
            "display_url": "nasa.gov",
            "expanded_url": "http://www.nasa.gov/",
            "indices": [
              0,
              23
            ],
            "url": "https://t.co/9NkQJKAnuU"
          }
        ]
      }
    },
    "protected": false,
    "isVerified": false,
    "isBlueVerified": true,
    "verifiedType": "Government",
    "followers": 92245753,
    "following": 115,
    "favouritesCount": 17110,
    "statusesCount": 74542,
    "mediaCount": 28249,
    "createdAt": "2007-12-19T20:20:32.000000Z",
    "coverPicture": "https://pbs.twimg.com/profile_banners/11348282/1788992290",
    "profilePicture": "https://pbs.twimg.com/profile_images/1321163587679784960/0ZxKlEKB_normal.jpg",
    "canDm": false,
    "affiliatesHighlightedLabel": {},
    "isAutomated": false,
    "automatedBy": null,
    "pinnedTweetIds": [],
    "profile_interstitial_type": ""
  }
}
```

A user that does not exist returns HTTP 200 with an error status, and is billed like a normal call:

```json
{
  "status": "error",
  "msg": "user not found",
  "data": null
}
```

#### 7. Get user about info

Returns the "About this account" panel: account based in, username changes and verification details where X shows them.

**Method:** `GET`

**Endpoint:** `/twitter/user_about`

**Parameters:**

| Name | In | Description | Type | Required | Default | Max Value |
|---|---|---|---|---|---|---|
| `userName` | query | Screen name without @ | string | Yes | - | - |

**Example Request:**

```bash
curl -X GET 'https://prod.api.market/api/v1/twitterapi-io/twitter-x-data/twitter/user_about?userName=NASA' \
  -H 'x-api-market-key: YOUR_API_KEY'
```

**Example Response (200 OK):**

```json
{
  "status": "success",
  "msg": "success",
  "data": {
    "id": "11348282",
    "name": "NASA",
    "userName": "NASA",
    "createdAt": "2007-12-19T20:20:32.000000Z",
    "profilePicture": "https://pbs.twimg.com/profile_images/1321163587679784960/0ZxKlEKB_normal.jpg",
    "isBlueVerified": true,
    "isVerified": false,
    "protected": false,
    "affiliates_highlighted_label": {},
    "identity_profile_labels_highlighted_label": {},
    "about_profile": {
      "learn_more_url": "https://help.twitter.com/managing-your-account/about-twitter-verified-accounts",
      "location_accurate": true,
      "username_changes": {
        "count": "0"
      }
    },
    "verification_info": {
      "id": "VXNlclZlcmlmaWNhdGlvbkluZm86MTEzNDgyODI=",
      "is_identity_verified": false,
      "reason": {
        "verified_since_msec": "1249674830941"
      }
    }
  }
}
```

#### 8. Get user followers

Returns a user's followers, most recent first, up to 200 per page.

**Method:** `GET`

**Endpoint:** `/twitter/user/followers`

**Parameters:**

| Name | In | Description | Type | Required | Default | Max Value |
|---|---|---|---|---|---|---|
| `userName` | query | Screen name without @ | string | Yes | - | - |
| `cursor` | query | `next_cursor` from the previous page | string | No | - | - |

**Example Request:**

```bash
curl -X GET 'https://prod.api.market/api/v1/twitterapi-io/twitter-x-data/twitter/user/followers?userName=NASA' \
  -H 'x-api-market-key: YOUR_API_KEY'
```

**Example Response (200 OK):**

```json
{
  "followers": [
    {
      "id": "1964817256568770560",
      "name": "ydfec",
      "userName": "yfr391",
      "followers_count": 48,
      "following_count": 3137
    }
  ],
  "has_next_page": true,
  "next_cursor": "CURSOR",
  "status": "success",
  "msg": "success",
  "code": 0
}
```

#### 9. Get user followings

Returns the accounts a user follows, most recent first, up to 200 per page.

**Method:** `GET`

**Endpoint:** `/twitter/user/followings`

**Parameters:**

| Name | In | Description | Type | Required | Default | Max Value |
|---|---|---|---|---|---|---|
| `userName` | query | Screen name without @ | string | Yes | - | - |
| `cursor` | query | `next_cursor` from the previous page | string | No | - | - |

**Example Request:**

```bash
curl -X GET 'https://prod.api.market/api/v1/twitterapi-io/twitter-x-data/twitter/user/followings?userName=NASA' \
  -H 'x-api-market-key: YOUR_API_KEY'
```

**Example Response (200 OK):**

```json
{
  "followings": [
    {
      "id": "2054998853900775424",
      "name": "Deputy Administrator Matt Anderson",
      "userName": "NASADepAdmin",
      "followers_count": 5740,
      "following_count": 6
    }
  ],
  "has_next_page": false,
  "next_cursor": "CURSOR",
  "status": "success",
  "msg": "success",
  "code": 0
}
```

#### 10. Check follow relationship

Returns whether one user follows another, and the reverse.

**Method:** `GET`

**Endpoint:** `/twitter/user/check_follow_relationship`

**Parameters:**

| Name | In | Description | Type | Required | Default | Max Value |
|---|---|---|---|---|---|---|
| `source_user_name` | query | The user who may follow | string | Yes | - | - |
| `target_user_name` | query | The user who may be followed | string | Yes | - | - |

**Example Request:**

```bash
curl -X GET 'https://prod.api.market/api/v1/twitterapi-io/twitter-x-data/twitter/user/check_follow_relationship?source_user_name=elonmusk&target_user_name=NASA' \
  -H 'x-api-market-key: YOUR_API_KEY'
```

**Example Response (200 OK):**

```json
{
  "status": "success",
  "message": "check follow relationship success",
  "data": {
    "following": true,
    "followed_by": false
  }
}
```

#### 11. Get trends

Returns trending topics for a location by Yahoo WOEID (1 is worldwide).

**Method:** `GET`

**Endpoint:** `/twitter/trends`

**Parameters:**

| Name | In | Description | Type | Required | Default | Max Value |
|---|---|---|---|---|---|---|
| `woeid` | query | Location id, `1` for worldwide | integer | Yes | - | - |
| `count` | query | Number of trends | integer | No | - | - |

**Example Request:**

```bash
curl -X GET 'https://prod.api.market/api/v1/twitterapi-io/twitter-x-data/twitter/trends?woeid=1&count=5' \
  -H 'x-api-market-key: YOUR_API_KEY'
```

**Example Response (200 OK):**

```json
{
  "status": "success",
  "msg": "success",
  "trends": [
    {
      "trend": {
        "name": "The FAA",
        "target": {
          "query": "\"The FAA\""
        },
        "rank": 1
      }
    },
    {
      "trend": {
        "name": "#シューイチ",
        "target": {
          "query": "#シューイチ"
        },
        "rank": 2
      }
    },
    {
      "trend": {
        "name": "Friday the 13th",
        "target": {
          "query": "\"Friday the 13th\""
        },
        "rank": 3
      }
    }
  ],
  "metadata": {
    "timestamp": 1794615183665,
    "refresh_interval_millis": 300000,
    "woeid": {
      "name": "Worldwide",
      "id": 1
    },
    "context_mode": "full"
  }
}
```

## Status Codes

| Code | Status | Description |
|---|---|---|
| 200 | OK | The request succeeded and the JSON result is in the response body. |
| 400 | Bad Request | A required parameter is missing or a value is not valid. |
| 401 | Unauthorized | The `x-api-market-key` header is missing or the key is not valid. |
| 403 | Forbidden | Your key does not have an active subscription that includes this endpoint. |
| 404 | Not Found | The path does not match an endpoint of this API. Check the Base URL and path. |
| 429 | Too Many Requests | You went over 10 requests per second or used up your plan. |
| 500 | Internal Server Error | The request failed on the server. Retry once, then contact us if it continues. |
| 503 | Service Unavailable | The service is temporarily unavailable. Retry after a short wait. |

## Rate Limits

Each subscriber can make up to 10 requests per second. The Free trial includes 1,000 units, and pay-as-you-go is billed $0.000125 per unit. Units depend on how much data a call returns: a full page of 20 tweets is about 30 units, a profile 2 units, a follow check 10 units and trends about 45 units. When you go over a limit, the API returns `429 Too Many Requests`. Throttle your requests, back off before retrying, and honour the `Retry-After` header when it is present.

## FAQ

*   **How are units counted?**
    Each call uses units based on the data it returns, for example about 30 units for a full page of 20 tweets and 2 units for a profile. Calls that fail with a 4xx or 5xx status use 0 units.

*   **Is a user that does not exist billed?**
    Yes. The lookup succeeds with HTTP 200 and `"status": "error"`, so it is billed like a normal profile call.

*   **Do I need X API keys?**
    No. Subscribe on API.market and call the endpoints with your API.market key.

*   **Can I get tweets from protected accounts?**
    No. Only public data is available.

*   **How do I get more than one page?**
    Send the `next_cursor` of the response as `cursor` in the next request until `has_next_page` is false.

## Contact Us

If you have any questions or need support, reach out through the chat embedded on this page or email us at hello@magicapi.com.


Read-only Twitter/X data API: advanced tweet search, user timelines, replies, quotes, mentions, profiles, followers and trends as JSON. No X keys needed.