Cookie Preferences
We use cookies to personalize content and analyze traffic. See our Cookie Policy.
No output yet. Submit the form to generate content.
Transparent pricing with no hidden fees. Pay as you go.
| Rule & Modality | Channel | Credits | Price (USD) | Official / Reference Price | Daily Savings |
|---|---|---|---|---|---|
user-by-screen-name otherTwitter | Starter | 0.01per post | $0.00005 | - | - |
Competitor pricing costs $45.450 more
ApiPass is 90.90% lower, estimated at multiple calls returning 10,000 returned posts total
user-by-screen-name
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Retrieve complete X (Twitter) user profile data instantly by passing a single screen_name — no OAuth, no rate-limit headaches, no manual GraphQL signing.
The Twitter Graphql User By Screen Name API on ApiPass is a managed endpoint that wraps X's internal UserByScreenName GraphQL operation behind a clean, asynchronous REST interface. Instead of dealing with guest tokens, query IDs, feature flags, or constantly-rotating GraphQL hashes, you simply POST a screen_name (e.g. elonmusk) to /api/v1/jobs/createTask with the model twitter/graphql/user-by-screen-name, and ApiPass returns a taskId you can poll via /api/v1/jobs/recordInfo — or receive automatically through a callBackUrl. The response delivers the full user object: rest_id, display name, bio, follower/following counts, verification status, profile and banner images, creation date, location, pinned tweet, highlighted label, and safety-mode fields. Under the hood, ApiPass's channel: auto router distributes each call across starter, regular, and official providers in real time to balance cost, stability, and speed — so you get production-grade Twitter user data without ever touching the /graphql/.../UserByScreenName path directly.
Skip the entire X developer portal flow. A single Authorization: Bearer YOUR_API_KEY header is all you need — no app review, no consumer keys, no access tokens.
User profile lookups on X's pay-per-use model cost around $0.010 each, and the free tier is no longer available to new developers, with existing users migrated to pay-per-use. ApiPass's multi-provider routing slots you into the cheapest stable channel automatically.
The channel: auto default lets APIPASS allocate each task across starter, regular, and official providers based on live pricing and stability metrics — you get the best price-to-reliability ratio without manual tuning.
Unlike X API v2, which only returns id/name/username by default and forces you to enumerate fields and expansions (the X API v2 version only delivers the user id, name, and username fields by default, and to request additional fields you need to use the fields and expansions parameters), the GraphQL endpoint returns the full, rich user object in a single call.
Fire-and-forget tasks return a taskId immediately; supply a callBackUrl and ApiPass pushes the result to your server the moment it's ready — perfect for serverless and queue-based architectures.
No 15-min rolling windows to manage in your own code, no guest-token refresh logic, no GraphQL query-hash drift — ApiPass absorbs all of that upstream so your application stays simple.
Pass screen_name: "elonmusk" and receive the complete user object — including rest_id, the canonical numeric user ID required by virtually every other Twitter GraphQL endpoint (UserTweets, Followers, Following, UserMedia, etc.).
Toggle withSafetyModeUserFields and withHighlightedLabel directly in the input.variables object to control which extended profile fields (safety-mode metadata, highlighted creator labels) appear in the response.
Every request flows through a consistent waiting → queuing → generating → success / fail state machine queryable via /api/v1/jobs/recordInfo, with createTime, completeTime, costTime, and resultJson returned in a predictable schema.
Convert any @handle into the stable numeric rest_id your downstream pipelines need.
Pull follower counts, verification badges, bio keywords, account age, and highlighted labels to score and rank profiles at scale.
Automatically validate that submitted Twitter handles exist, are active, are not protected, and match expected metadata before approving signups, giveaways, or KOL partnerships.
Enrich any contact record that includes a Twitter handle with profile picture, location, website URL, follower count, and creation date in milliseconds.
While X's official API gates user lookups behind developer approval, tiered pricing, and sparse default fields, ApiPass delivers the full GraphQL profile object through one simple, auto-routed, pay-per-task call.
The official GET /2/users/by/username/:username endpoint requires you to manually expand fields via query params, and only delivers id, name, and username by default — additional fields require fields and expansions parameters. ApiPass's GraphQL wrapper returns the full native user object (including pinned tweets, professional-account info, verification type, and highlighted labels) in one call with no fields= enumeration.
X has consolidated access into a usage-based model where creating a post costs about 0.010, reading a post costs about 0.005, and user profile lookups and DM reads cost around $0.010 each, layered on top of monthly caps. ApiPass charges per successful task only, routes you to the lowest-cost stable provider by default, and imposes no developer-portal application step.
Resolve every mentioned handle in a stream of tweets into a full profile so analysts can filter by follower size, verification status, or account age.
Confirm a wallet-linked Twitter handle is real, sufficiently old, and meets follower thresholds before issuing tokens, NFTs, or whitelist spots.
Quickly pull authoritative metadata (creation date, location, profile history signals, highlighted labels) on any public account under investigation.
Enrich candidate Twitter handles with bio, website URL, and follower counts to surface developer advocates, designers, and creators for outreach.
Sign up at ApiPass and grab your YOUR_API_KEY from the dashboard. No developer-portal application, no OAuth setup, and no app review required — a single bearer token unlocks every model on the platform.
Send a POST request to https://api.apipass.dev/api/v1/jobs/createTask with the model set to twitter/graphql/user-by-screen-name and provide your target handle inside input.variables.screen_name (for example, elonmusk). Optionally include withSafetyModeUserFields and withHighlightedLabel to enrich the response, and pass a callBackUrl if you'd like ApiPass to push the result to your server automatically. The API will respond immediately with a taskId such as task_12345678.
Either wait for ApiPass to POST the completed payload to your callBackUrl, or poll https://api.apipass.dev/api/v1/jobs/recordInfo?taskId=task_12345678 with your bearer token. Once data.state becomes success, the full user profile — including rest_id, bio, follower and following counts, verification status, profile images, creation date, and any requested optional fields — will be available inside data.resultJson.resultObject. That's it: you're now pulling Twitter GraphQL user data in production.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get user information by screen_name
The API accepts a JSON payload with the following structure:
1{
2 "model": "string",
3 "callBackUrl": "string (optional)",
4 "channel": "auto",
5 "input": {
6 "variables": {
7 "screen_name": "string",
8 "withSafetyModeUserFields": "boolean",
9 "withHighlightedLabel": "boolean",
10 }
11 }
12}modelRequiredstringThe model name to use for generation
"twitter/graphql/user-by-screen-name"
callBackUrlOptionalstringCallback URL for task completion notifications. If omitted, no callback will be sent.
"https://your-domain.com/api/callback"
channelOptionalstringYou may specify the corresponding provider within APIPASS via the channel parameter; these providers handle the actual image and video generation tasks. APIPASS currently offers three provider options:
The default value for the channel parameter is auto. When enabled, APIPASS automatically allocates tasks across available providers based on real-time pricing and stability metrics to balance minimal cost and reliable performance. Retain the default auto value unless you have custom routing requirements.
Available options:
auto
The input object contains the following parameters:
input.variables.screen_nameRequiredstringelonmusk
input.variables.withSafetyModeUserFieldsOptionalbooleantrue
input.variables.withHighlightedLabelOptionalbooleantrue
1curl -X POST "https://api.apipass.dev/api/v1/jobs/createTask" \
2 -H "Content-Type: application/json" \
3 -H "Authorization: Bearer YOUR_API_KEY" \
4 -d '{
5 "model": "twitter/graphql/user-by-screen-name",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "variables": {
9 "screen_name": "elonmusk",
10 "withSafetyModeUserFields": true,
11 "withHighlightedLabel": true
12 }
13 }
14 }'1{
2 "code": 200,
3 "message": "success",
4 "data": {
5 "taskId": "task_12345678"
6 }
7}codeStatus code, 200 for success, others for failure
messageResponse message, error description when failed
data.taskIdTask ID for querying task status and results
