GET https://xquik.com/api/v1/x/users/{id}/following
When to read outbound relationships
Use this route for accounts the selected user follows. Use followers for inbound relationships. Use verified followers when you need only verified inbound followers.1 credit per result returned · All plans from $0.00012/credit
GET /api/v1/x/users/{id}/following.Omit
mode to get the fullest results. The response shape stays the same.
Pass next_cursor back unchanged as cursor. Keep the same endpoint, target,
query, and filters.after, limit, and
pageSize aliases also keep working. Billing still counts only returned rows.
Use mode=standard only to keep the legacy pagination.A page can be empty or underfilled. Continue while has_next_page is true.
Stop only after the response reports has_next_page=false.First-page requests do not support Idempotency-Key retries.
Repeating a cursorless request starts a separate extraction.
Results returned by that extraction incur their normal charges.
Save each response before requesting its next page.
A cursor sent again within 10 minutes returns the same page at no charge.
After 10 minutes, you cannot replay earlier or terminal responses.If automatic coverage is busy, an initial request returns a standard data page.
Live coverage cursors remain atomic. A cursor sent again while its page loads
returns that page at no charge.
Other repeats return 409 coverage_cursor_unavailable with exact Retry-After
seconds. Wait, then send the same cursor again.
Repeated busy responses never authorize restarting with another cursor.Expired, superseded, or identity-mismatched cursors return
410 coverage_cursor_gone. So does a cursor sent again after 10 minutes. The
response omits Retry-After. Restart without a cursor. Keep received results.
Deduplicate restarted results by id.
Malformed cursors return 400 invalid_coverage_cursor. Restart without them.next_cursor in your
sync job. It can then resume from the last completed page.
For high-volume following pulls, deduplicate profiles by id. Continue through empty pages while the cursor advances. Stop with a partial-result status when next_cursor is missing or repeats.Direct following handoff
For one paginated JSON page of a user’s followed accounts now, useGET /x/users/{id}/following. It suits a CRM, warehouse, audience, or agent workflow. The endpoint accepts a username or numeric user ID. It returns followed account profile rows with cursor fields. For estimated jobs, saved extractions, or CSV, JSON, or XLSX file export, use following_explorer.Following rows
Store
users[] as the followed account profile rows returned on this page.Stable upserts
Store
users[].id as x_user_id for CRM, warehouse, audience, and agent deduplication.Readable labels
Store
users[].username and users[].name for handles, labels, segments, and review queues.Profile enrichment
Store
users[].description, location, url, profilePicture, and coverPicture when returned.Next page
Store
has_next_page and next_cursor. Then pass next_cursor back as cursor only when has_next_page is true.Page size
Automatic pages accept 20 to 10,000. Standard pages accept 20 to 200.
402 insufficient_credits.Track Twitter following changes
An account monitor reports each change for you. Selectfollowing.added and following.removed. Each event holds the
other account’s profile, or its ID when X shows none. Add
profile.following.changed for count moves.
Use this endpoint for the starting list. Store every cursor page before
advancing. Key rows by user ID, since usernames change.Path parameters
Query parameters
Choose fields
Which following endpoint?
One user's following
Use
GET /x/users/{id}/following for the accounts one profile follows.One user's followers
Use
GET /x/users/{id}/followers for the
accounts that follow that profile.Verified followers
Use
GET /x/users/{id}/verified-followers
when you only need verified followers of the profile.Saved exports
Use
following_explorer for a saved
following extraction with CSV, JSON, or XLSX download handoff.User result filters
These filters apply before billing. Selective filters can return fewer rows.See user filters for every filter. Common ones areminFollowers, verifiedOnly, hasWebsite, hasEmail, bioContains, and locationContains.Headers
Response
200 OK
WithenrichProfiles=true, each row carries the full profile. The
x-xquik-profile-enrichment header then counts the rows that have it, as in
enriched=180; requested=200. A row without it keeps its list fields.400 Invalid user ID
{ "error": "invalid_user_id", "message": "Send a user ID, @username or profile URL, such as x.com/nasa." }401 Unauthenticated
Anonymous requests getWWW-Authenticate: Bearer and a guest wallet checkout action. This is not a Payment challenge.402 Payment required
Account keys get account options. Guest keys get guest top-up only. No checkout starts automatically. Confirm any payment action.502 X API unavailable
The read service returned an error. Retry after a short delay.429 Rate limit exceeded
You exceeded your tier rate limit. Wait for theRetry-After header before retrying.424 Dependency failed
The normalized v1 response contract can return 424 when the read service is unavailable.Related. Get followers · Get verified followers · Get followers you know
Response examples
- 400
{ "error": "invalid_input", "message": "Invalid input. Check the request body." } - 401
{ "error": "unauthenticated", "message": "Authentication required." } - 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": "user_not_found", "message": "X user not found. Check the username." } - 409
{ "error": "coverage_cursor_unavailable", "message": "Cursor busy. Retry after the indicated delay." } - 410
{ "error": "coverage_cursor_gone", "message": "Cursor finished, expired, or superseded. Restart pagination without cursor." } - 424
{ "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." } - 429
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 } - 502
{ "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." } - 503
{ "error": "x_api_unavailable", "message": "Maximum coverage is busy. Retry shortly." }