Skip to main content
GET
Twitter following IDs API & fast friend list export
Requested result counts are upper bounds for paid authenticated calls. When remaining credits cannot cover the full page or ID list, Xquik returns fewer results. If zero paid results are affordable, it returns 402 insufficient_credits.
1 credit per result returned · All plans from $0.00012/credit · Supports guest paid reads

IDs only, 5,000 a page

Use GET /x/users/{id}/following-ids for the user IDs of the accounts a user follows. IDs arrive newest first. The response holds no profiles, so a page holds up to 5,000 IDs. Use it for fast audience syncs and set comparisons. Pass up to 100 IDs to GET /x/users/batch when you need profiles. Stop paging when has_next_page is false. A protected account returns 403 x_account_protected. Xquik charges nothing.

IDs or profiles?

  • Use GET /api/v1/x/users/{id}/following-ids when IDs are enough.
  • Use GET /api/v1/x/users/{id}/following when each row needs a profile.

Path parameters

string
required
User ID, username with or without @, or URL-encoded profile URL, such as x.com/nasa. See path IDs.

Query parameters

string
Pagination cursor. Pass the next_cursor value from the previous response to fetch the next page.
integer
User IDs per page. Range: 1-5000. Defaults to 5000.

Headers

string
Full account key. Sessions and OAuth also work.
string
Bearer xq_your_guest_key_here for paid_reads.

Response

200 OK

string[]
User IDs, newest first.
boolean
Whether more results are available.
string
Opaque cursor for the next page. Empty string when no more results.

400 Invalid user ID

The user ID is empty or invalid.

403 Protected account

404 User not found

401 Unauthenticated

Anonymous requests get WWW-Authenticate: Bearer and a guest wallet checkout action. This is not a Payment challenge.
Missing or invalid API key.

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 the Retry-After header before retrying.

424 Dependency failed

The normalized v1 response contract can return 424 when the read service is unavailable.