X (Twitter) Following list API

Request parameters

Code samples

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "twitter",
  "action": "following_list",
  "params": {
    "username": "nasa"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

{
  "id": "req_…",
  "platform": "twitter",
  "action": "following_list",
  "results": [
    {
      "id": "（已隐去）",
      "username": "（已隐去）",
      "url": "https://x.com/（已隐去）",
      "name": "（已隐去）",
      "text": "Serving President Donald J. Trump as the 16th @NASA Deputy Administrator | Working alongside @（已隐去） to lead the next Golden Age of space discovery 🚀",
      "avatar_url": "https://pbs.twimg.com/（已隐去）",
      "follower_count": 5417,
      "following_count": 6,
      "post_count": 64,
      "is_verified": false,
      "is_protected": false,
      "created_at": "Thu May 14 18:55:50 +0000 2026",
      "platform": "twitter"
    },
    {
      "id": "（已隐去）",
      "username": "（已隐去）",
      "url": "https://x.com/（已隐去）",
      "name": "（已隐去）",
      "text": "@（已隐去） astronaut. Artemis II crewmember | Astronaute @（已隐去） Membre de l’équipage d’Artemis II",
      "location": "（已隐去）",
      "avatar_url": "https://pbs.twimg.com/（已隐去）",
      "follower_count": 149812,
      "following_count": 155,
      "post_count": 2844,
      "is_verified": false,
      "is_protected": false,
      "created_at": "Tue Aug 09 14:55:39 +0000 2011",
      "platform": "twitter"
    }
  ],
  "count": 115,
  "billing": { … },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the source does not provide are never made up.

Errors and billing

401

Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.

422

Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.

402

Insufficient balance. Top up first.

429

Per-minute request limit reached. Wait for Retry-After and try again.

503

Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.

200 empty

The request completed without data and is not charged (billing.reason = empty_result_refunded).

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

• X: Direction of Followers vs. Following ↗

  X separately explains who follows you and who you follow, as following does not need to be mutual; protected posts have additional access restrictions. List queries are not bulk-follow actions and do not imply expanded access permissions.

  Checked 2026-09-04