Docs
Account status for many handles

Account status for many handles

Whether each handle is active, suspended, protected or not found. Up to 500 handles per call.

GET/user/usernames/status

Free tool: Shadowban checker, no API key needed.

Parameters

  • usernamesquery · string (comma-separated) · required

    Handles separated by commas, with or without @. At most 500.

Example request

curl 'https://api.twittrapi.com/user/usernames/status?usernames=jack,XDevelopers' \
  --header 'X-API-KEY: YOUR_API_KEY'

Base URL https://api.twittrapi.com, key in the X-API-KEY header. Python and Node.js use the official SDKs.

Response

Built by the API: {"usernamesStatus": {"jack": "active", ...}}. Values: active, suspended, protected, not-found, or error when X could not be asked. For each error there is also an entry in errors: [{"username": "...", "error": "upstream_error", "message": "..."}]; errors is left out when there are none.

Simple format (?format=simple or X-Response-Format: simple): Unchanged inside {data: ...}: {usernamesStatus, errors} is already small, so the simple format only adds the envelope. Schema.

{
  "usernamesStatus": {
    "XDevelopers": "active",
    "jack": "active"
  }
}

In the raw format, field names and nesting come from X and can change without notice. See Response format; the simple format keeps a fixed schema.

Errors

  • 400usernames is missing or has more than 500 entries.

Errors every endpoint can return (401, 402, 403, 404, 408, 409, 429, 5xx), and which of them are charged, are on the Errors page. Calls that fail with 400, 408, 409 or a 5xx error are refunded.