Account status for many handles
Whether each handle is active, suspended, protected or not found. Up to 500 handles per call.
Reference: https://www.twittrapi.com/docs/reference/user-usernames-status
Request
- Base URL: https://api.twittrapi.com
- URL: https://api.twittrapi.com/user/usernames/status
- Auth: API key in header X-API-KEY
Query parameters
Handles separated by commas, with or without @. At most 500.
raw (default): X's JSON passed through. simple: flat camelCase JSON with a fixed schema and a {data, nextCursor, previousCursor, hasNextPage} envelope. Same price. The header X-Response-Format: simple does the same.
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.
With format=simple: Unchanged inside {data: ...}: {usernamesStatus, errors} is already small, so the simple format only adds the envelope.
Changes
No recorded changes to this operation across all 1 revision of this API.