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 |
|---|---|---|---|---|---|
favorite-tweet 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
favorite-tweet
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Automate tweet likes at scale with a single API call — programmatically favorite any public tweet on X (Twitter) using ApiPass's asynchronous job-based endpoint.
The Twitter Graphql Favorite Tweet API on ApiPass is an asynchronous endpoint that lets you programmatically like (favorite) tweets on X (formerly Twitter) using the underlying GraphQL protocol that powers the official X web client. By submitting a target tweet_id along with your X account's auth_token, ApiPass dispatches the task through its intelligent provider routing system and returns a taskId you can poll — or receive via callback — to confirm the like action was successfully executed. It abstracts away the complexity of GraphQL query hashes, header signing, and rate-limit handling, giving developers a clean REST-style interface to one of Twitter's most-used engagement actions.
Skip the pain of reverse-engineering Twitter's GraphQL endpoints, query IDs, and shifting request signatures. ApiPass wraps everything in a clean JSON POST request.
The default auto channel dynamically allocates tasks across starter, regular, and official providers based on real-time pricing and stability, keeping your costs low without sacrificing reliability.
Tasks are queued and processed in the background. Poll /jobs/recordInfo or register a callBackUrl to be notified the moment the like is completed.
Use your own X auth_token cookie, meaning likes are performed from a real, fully-functional account with normal engagement footprint.
ApiPass pricing sits far below Twitter's official Enterprise API tier, making automated engagement workflows economically feasible for indie developers and growth teams.
Configure a callBackUrl in the request payload and ApiPass will push completion notifications to your server — no polling loops required.
Send just a tweet_id inside the variables object and the API handles the rest, from GraphQL payload construction to response parsing.
Choose between starter, regular, and official channels, or let auto pick the optimal provider for each request.
Every request returns a persistent taskId with clear state transitions (waiting → queuing → generating → success/fail) for full observability.
Build agents that like tweets from specific creators, hashtags, or topics on your behalf as part of a broader social listening workflow.
Power SaaS products that help creators and marketers engage authentically with their target audience at scale.
Trigger a like as an on-chain or off-chain reward action when a user completes a task in your Web3 or gamified app.
Connect your CRM so that liking a customer's tweet becomes a scheduled follow-up action after a support case is resolved.
See how ApiPass's favorite-tweet endpoint stacks up against X's official API in terms of accessibility, pricing, and developer experience — and why teams choose ApiPass to ship faster.
Twitter's official API (X API v2) restricts the POST /2/users/:id/likes endpoint to paid tiers with steep monthly fees and strict rate caps. ApiPass offers per-task pricing with no minimum commitment, making it accessible to solo builders and prototype projects.
The official API requires OAuth 2.0 app registration, developer portal approval, and per-user token exchange flows. ApiPass only needs an AuthToken cookie from a logged-in X session, dramatically reducing time-to-first-like from days to minutes.
Automatically like tweets that mention your brand or product to boost visibility and signal acknowledgement to your community.
Have your monitoring tool auto-like posts from partnered creators once they publish sponsored content matching a campaign hashtag.
Give autonomous AI agents the ability to express approval on X by liking tweets that align with their configured interests or user instructions.
Turn "likes" into a curation signal — automatically favorite tweets your ML pipeline classifies as high-value so they surface in your bookmarks and downstream feeds.
Sign up on ApiPass to obtain your API_KEY, then grab your X auth_token from the browser (F12 → Application → Cookies → auth_token on twitter.com while logged in).
Send a POST to /api/v1/jobs/createTask with model: "twitter/graphql/favorite-tweet", your AuthToken, and the target tweet_id inside input.variables. ApiPass responds with a taskId.
Poll GET /api/v1/jobs/recordInfo?taskId=... until state becomes success, or configure a callBackUrl in the original request to receive an automatic push notification when the like has been executed.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Like a tweet.
The API accepts a JSON payload with the following structure:
1{
2 "model": "string",
3 "callBackUrl": "string (optional)",
4 "channel": "auto",
5 "input": {
6 "AuthToken": "string",
7 "variables": {
8 "tweet_id": "string"
9 }
10 }
11}modelRequiredstringThe model name to use for generation
"twitter/graphql/favorite-tweet"
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.tweet_idRequiredstring123
input.AuthTokenRequiredstringOpen the Twitter homepage, log in, then go to F12 > Application > Storage > Cookies > auth_token.
YOUR_X_AUTH_TOKEN
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/favorite-tweet",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "AuthToken": "YOUR_X_AUTH_TOKEN",
9 "variables": {
10 "tweet_id": "1852944751370109241"
11 }
12 }
13 }'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
