Users

Following

Accounts a user follows.

Also answers on: GET /user/{userId}/following (same handler).

Paginated: pass the bottom cursor of one page as cursor to get the next. Each page is one billed call.

Reference: https://www.twittrapi.com/docs/reference/user-userid-followings

get/user/{userId}/followings

Request

  • Base URL: https://api.twittrapi.com
  • URL: https://api.twittrapi.com/user/{userId}/followings
  • Auth: API key in header X-API-KEY

Path parameters

userIdstring required

Numeric user ID (digits only, up to 30). To pass a handle instead, use -1 here and set username.

Query parameters

usernamestring

Handle, with or without @. When set, it is used instead of userId: the API looks up the ID first, which makes the call a little slower. Still one billed call.

countinteger

Number of items to ask X for. Sent to X as is; X treats it as a hint and decides how many it returns (follower and following pages often hold 50 to 70 users for count=20). A value that is not a number falls back to 20.

cursorstring

Bottom cursor from the previous page. Leave it out for the first page. See Pagination.

format'raw' | 'simple'

raw (default): X's JSON passed through. simple: flat camelCase JSON with a fixed schema and a {data, nextCursor, previousCursor, hasNextPage} envelope. Same price. The header X-Response-Format: simple does the same.

Response

Raw JSON of X's Following query.

With format=simple: Collection of User objects: {data: [User], nextCursor, previousCursor, hasNextPage}.

OR
RawPassthrough required

X's own JSON (raw format, the default), passed through unchanged. The shape is X's and can change; see https://www.twittrapi.com/docs/response-format.

Changes

No recorded changes to this operation across all 1 revision of this API.