Social Fetch
Get API key
X (Twitter) hub

X (Twitter) Profile API

Resolve a public X handle to a profile card — display name, bio, avatar, and follower-style metrics — with Social Fetch's shared response envelope.

GET /v1/twitter/profiles/{handle}

1 credit per successful request.

Try in playgroundFull API docs

About this endpoint

Most products that touch X only need a public profile card: confirm the handle exists, pull the bio and avatar, and read follower or post counts for scoring. That job does not require an X developer app, write scopes, or elevated access tiers.

`GET /v1/twitter/profiles/{handle}` is the dedicated route for that lookup. Pass the handle (with or without a leading `@`, per the docs), send `x-api-key`, and read `data.lookupStatus` before you write a row. On `found`, `data.profile` and `data.metrics` carry the public card; `meta.creditsCharged` records what the call cost.

Credit pricing for this operation comes from the API registry and appears on this page and in the docs — do not assume every Twitter route costs the same. For timelines, use the separate profile-tweets list route; this endpoint stops at the profile card.

X (Twitter) Profile API FAQ

How do I fetch an X / Twitter profile by handle?

Call GET /v1/twitter/profiles/{handle} with your Social Fetch API key in the x-api-key header. The handle is the public @username. Full parameters and examples are in the API docs linked from this page.

How many credits does a Twitter profile lookup cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth. Failed lookups that Social Fetch marks as non-billable do not consume credits.

Do I need an X developer account or Bearer token?

No. Social Fetch authenticates with your Social Fetch API key only. You do not create an X developer app or pass X credentials for this public profile route.

What happens for private, suspended, or missing accounts?

We do not invent public data for inaccessible accounts. Read data.lookupStatus (and related typed outcomes in the docs) before treating the payload as a found profile. Retry only on documented transient failures — not on not-found.

What does the profile response include?

On a found lookup, the envelope includes a profile object (handle, display name, bio, avatar, and related public fields) plus metrics such as follower and post counts where available. Exact field lists and nullability live in the OpenAPI schema for this route.

Is this the same as listing a user's tweets?

No. This endpoint returns the profile card only. To list posts for a handle, use GET /v1/twitter/profiles/{handle}/tweets (a separate marketplace operation with its own credit note).

Can I use this for enrichment or monitoring jobs?

Yes. Teams use the profile route to hydrate CRM or creator records, verify handles before monitoring, and refresh public metrics on a schedule. Pair it with search or tweet routes when the job needs content, not just identity.

Other X (Twitter) endpoints