POST https://xquik.com/api/v1/x/users/{id}/follow
Follow one Twitter user by ID
Each request follows 1 target user ID. Each request names 1 connected X account. Verify the target user ID. Approve the acting account before sending the action. Compare X’s separate Follow User endpoint.10 credits per call · All plans from $0.00012/credit
Authenticate and approve the follow
Send an Xquik API key or OAuth 2.1 bearer token. Never send an X password or session cookie. Show the target user ID, username, profile name, and acting account.Verify the Twitter follow API result
Store the target ID, acting account, action ID, and request hash. PollstatusUrl until terminal becomes true.
Close already-followed results without another request.
Use Check Follower when you need current proof.
Use Following to read outbound relationships.
Use Unfollow User to reverse approval.Handle Twitter follow API errors
Fix the user ID or account after400.
Replace Xquik authentication after 401. Reconnect after 403.
Add credits after 402. Review rejected input after 422.
Honor Retry-After after 429.
After 500 or 503, check safeToRetry before retrying.Twitter API follow questions
How do I follow a user programmatically?
Approve the target user ID and connected account. Send this POST request. Poll the returned action until terminal.Can I follow a protected X account?
Protected X profiles may keep follows pending until approval. Verify the relationship before dependent work begins.Can I bulk follow Twitter users?
No bulk request exists here. Send 1 approved target ID per action and respect both limits above.Do I need a Twitter follow SDK?
No. Use any HTTP client or the cURL, Node.js, Python, and Go examples. A third-party app still needs an approved connected account.How do I check or undo a follow?
Use Check Follower for current proof. Use Unfollow User with new approval and a new idempotency key.Headers
Path parameters
Body
Response
Durable write recovery
- Store
id, the nestedhashinrequest,billing, andstatusUrl. - Poll after
Retry-AfterorpollAfterMswhenterminalisfalse. - Retry only when
safeToRetryistrue. - Use a new key when
nextAction.requiresNewIdempotencyKeyistrue.
200 terminal or 202 active
- After HTTP
200, store the result and settled billing. - After HTTP
202, poll the same action. Never submit another write. - After HTTP
400, fix the named field. Use a new idempotency key. - After HTTP
401, fix authentication. Do not retry unchanged. - After HTTP
402, fund the account before another write. - After HTTP
403, reconnect the account. - After HTTP
409, keep the original action. Use a new key for new input. - After HTTP
422, fix the rejected request before retrying. - After HTTP
429, wait forRetry-After. FollownextAction.
Response examples
200 example
202 example
- 400
{ "error": "missing_idempotency_key", "message": "Idempotency-Key is required. Generate one unique key for this write.", "charged": false, "chargedCredits": "0", "retryable": false, "safeToRetry": true } - 401
{ "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." } - 402
{ "error": "insufficient_credits", "message": "Insufficient credits. Top up or subscribe to continue." } - 403
{ "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." } - 404
{ "error": "account_not_found", "message": "X account not found. Connect it first at /dashboard/x-accounts." } - 409
{ "error": "idempotency_conflict", "message": "Idempotency-Key was already used with a different request.", "charged": false, "chargedCredits": "0", "retryable": false, "safeToRetry": true } - 422
{ "error": "x_rejected", "message": "X rejected this request. Check what you sent & the account on x.com before you try again." } - 429
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 } - 500
{ "error": "x_write_failed", "message": "Write action failed unexpectedly. Contact support if this persists." } - 503
{ "error": "write_tracking_unavailable", "message": "Write tracking unavailable. Try again.", "charged": false, "chargedCredits": "0", "retryable": true, "safeToRetry": true }