X (Twitter) Details API

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra X (Twitter) Details endpoint (twitter/profile).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to twitter and action to profile, and put the parameters inside params.
- Required parameters:
  - username: X username, optionally prefixed with @, without entering a full profile URL. profile compiles data from author details within recent posts.
- Returns one object. Main fields: user_id, username, display_name, bio, url, follower_count, following_count, post_count, is_verified, location, avatar_url, created_at.
- Example request body:
{
  "platform": "twitter",
  "action": "profile",
  "params": {
    "username": "nasa"
  }
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

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": "profile",
  "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": "profile",
  "results": {
    "user_id": "（已隐去）",
    "username": "NASA",
    "display_name": "NASA",
    "url": "https://x.com/NASA",
    "follower_count": 92375075,
    "following_count": 115,
    "post_count": 74334,
    "is_verified": true,
    "location": "Pale Blue Dot",
    "avatar_url": "https://pbs.twimg.com/（已隐去）",
    "created_at": "Wed Dec 19 20:20:32 +0000 2007",
    "platform": "twitter"
  },
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

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

FAQ

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

The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.

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: username / handle vs. Display Name ↗

  X separates the handle from the display name; the handle forms the @ identifier and profile link, and once changed, the original handle may be claimed by others. When archiving, do not rely solely on display names or mutable handles to verify identity.

  Checked 2026-09-04