# X user search

X user search: inspect inputs, account fields, pagination and limits, then run a local simulated request.

Canonical page: https://datanavoapi.com/en/apis/x/users/search/

This is a local simulation. Program-generated samples are not live platform data and do not establish provider availability.

## What this capability does

X user search uses /v1/x/users/search; GET returns data.items with account objects.

This is a local simulation. Program-generated samples are not live platform data and do not establish provider availability.

- Capability: x.users.search
- Pagination: use the signed cursor from the response and request each page explicitly.

## Input contract

Inspect meanings, examples and conditional rules for the selected method. view and fields control the response without changing the TEST unit price.

- Only send fields defined for this method; unknown fields are rejected before execution.

| Method | Field | Type | Requirement | Meaning | Enum or bound | Example |

| --- | --- | --- | --- | --- | --- | --- |

| GET | query | string | Required | Search terms | — | "Smithsonian" |

| GET | cursor | string | Optional / conditional | The `next_cursor` of the previous page. A new page is a new call. | — | — |

| GET | view | string | Optional / conditional | How much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`). | ["compact","standard","full"] | — |

| GET | fields | array | Optional / conditional | Return only these fields of each item, by path (`author.name`). | maxItems: 64 | — |

## Try it locally

Use demo to inspect the fields, then explicitly select simulated with a customer test key to exercise settlement. Never put a customer key in a URL.

```json
{
  "capability": "x.users.search",
  "method": "GET",
  "params": {
    "query": "Smithsonian"
  }
}
```

- [Open this capability in the console](https://datanavoapi.com/console/?mode=demo&capability=x.users.search&method=GET&params=%7B%22query%22%3A%22Smithsonian%22%7D)

## Output fields and interpretation

The account object permits missing or null values; do not replace missing measurements with zero. This table shows the main structure; the object reference covers nested fields.

| Field | Type | Meaning | Source scope |

| --- | --- | --- | --- |

| id | string \| null | ID | X (Twitter) |

| username | string \| null | Handle | X (Twitter) |

| name | string \| null | Display name | X (Twitter) |

| url | string \| null | Link to the profile | X (Twitter) |

| bio | string \| null | Bio | X (Twitter) |

| avatar_url | string \| null | Avatar (standard view and up) | X (Twitter) |

| verified | boolean \| null | Whether the account is verified (standard view and up) | X (Twitter) |

| created_at | string \| null | When the account was created (standard view and up) | X (Twitter) |

| metrics | object \| null | Account counts | X (Twitter) |

| metrics.followers | integer \| null | Followers | X (Twitter) |

| metrics.following | integer \| null | Following | X (Twitter) |

| metrics.posts | integer \| null | Posts published | X (Twitter) |

| approximate | array \| null | Which numbers of this item are approximate or lower bounds; absent when all are exact | X (Twitter) |

| approximate[].field | string \| null | Path of the field, such as metrics.views | X (Twitter) |

| approximate[].kind | string \| null | Approximate, or a lower bound | X (Twitter) |

| ext | object | — | X (Twitter) |

| ext.website | string \| null | The website the page gives (full view) | X (Twitter) |

| ext.verified_type | string \| null | Kind of verification: person (an individual, the orange or gold V) or organization (the blue V of a company, a media outlet, a government body and the like); null when not verified (full view) | X (Twitter) |

| ext.location | string \| null | The region given on the profile (北京, 广东 深圳, say; 其他 where none was given), not the IP location (full view) | X (Twitter) |

- [Complete object reference](https://datanavoapi.com/en/docs/objects/account/)

## Unavailable fields

These published contract notes describe the capability boundary; fixtures do not establish live availability.

| Field | Reason |

| --- | --- |

## Limits and checks

A successful request does not establish full coverage. Preserve the request ID, observation time, parameters and cursor, and inspect the returned items before analysis.

Local simulation uses TEST credits only. Real provider calls, real payments and external email are disabled. Historical reference-site prices are not DataNavoAPI prices.

- Verify media URLs, counts and optional fields individually.

## Related pages

- [X (Twitter) APIs](https://datanavoapi.com/en/apis/x/)
- [X (Twitter) MCP](https://datanavoapi.com/en/mcp/x/)
- [Account fields](https://datanavoapi.com/en/docs/objects/account/)

[中文](https://datanavoapi.com/apis/x/users/search/)
