Social API·15 credits per call

Access public Twitter profile metadata instantly.

Provide a username and receive structured JSON profile data. Skip the complexity of managing rotating headers or official developer application waitlists.

POSTautomatio.ai/api/v1/query{ tool: "twitter_user", params: { username: … } }

Live demo

Try it live.

Change the parameters and run a real request against the endpoint. No account, no key.

Usernamerequired

Free to try, no account. Costs 15 credits on your own key.

POST /api/v1/query · twitter_user

Run the request to see a live response.

Request
curl -X POST https://automatio.ai/api/v1/query \
  -H "Authorization: Bearer $AUTOMATIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tool":"twitter_user","params":{"username":"vercel"}}'

How it works

One request, one response.

  1. 1

    Send username

    Provide the target Twitter handle as a string in the tool parameters.

  2. 2

    Fetch profile

    The system retrieves the latest public profile information from the platform.

  3. 3

    Receive JSON

    You get a structured object containing bio details, engagement counts, and account status.

Capabilities

What you get.

Everything this endpoint does, without running the infrastructure yourself.

Profile metadata

Retrieves account biographies, display names, and profile imagery URLs.

Engagement metrics

Returns live counts for followers, following, and total tweet volume.

Account status

Identifies verified status and account creation dates for trust signals.

No session management

Handles data extraction without requiring the caller to maintain platform-specific cookies.

Cost of ownership

Build it yourself, or call this.

Both are real options. Here is what each one actually costs you.

Run it yourself

  • Managing scrapers or headless browsers
  • Handling platform anti-bot measures and IP rotation
  • Parsing inconsistent HTML into structured data
  • Maintaining code as the platform DOM changes

Call the API

  • Single POST request for any profile
  • Fixed credit cost per successful retrieval
  • Data returned in consistent JSON schema
  • Access via standard HTTP or MCP-compatible clients

Integrate

Built for the language you use.

One HTTP endpoint. Copy the call in your language and go.

example.sh
curl -X POST https://automatio.ai/api/v1/query \
  -H "Authorization: Bearer $AUTOMATIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "tool": "twitter_user", "params": { "username": "spez" } }'

In production

What people build with it.

Lead Enrichment

A CRM system takes a list of handles and calls this endpoint to update follower counts and bios automatically. This allows sales teams to prioritize outreach based on social reach and influence without manual research.

Influence Monitoring

An analytics dashboard tracks a list of competitors to detect sudden shifts in follower growth or changes in their public messaging. It provides a daily snapshot of account health to identify trending creators.

Identity Verification

An onboarding flow checks a user's provided handle to confirm their account age and verified status. This helps flag potential bot accounts or brand new profiles during the registration process for security.

Choosing parameters

Which options matter.

The table below lists what exists. These are the calls worth making deliberately.

username
Provide the handle without the @ symbol. The endpoint expects a plain string value and will return an error if the handle contains spaces or invalid characters.

Alternatives

When to use something else.

A page that pretends it has no alternatives reads as an advert. These are the other real options.

Official X API

Best for high-volume writes and official integrations, but requires a paid subscription tier and a lengthy app approval process.

Manual scraping

Allows for complete control over the extraction process, but requires significant infrastructure to handle blocking and DOM updates.

Before you integrate

What it does not do.

The boundaries are as useful as the features. These are the ones worth knowing up front.

Public accounts only

This endpoint cannot retrieve data from private or protected accounts. If the profile is locked, the request will return null values for sensitive fields or a tool-level error.

No tweet history

This tool focuses strictly on profile metadata. To retrieve a timeline of posts, you must use the twitter_user_tweets endpoint instead.

Real-time latency

Responses are fetched live to ensure accuracy, which takes longer than querying a cached database. Expect a brief delay as the platform is queried for the latest data.

Reference

15 credits per call
Endpoint
POST https://automatio.ai/api/v1/query
Tool ID
twitter_user

Parameters

NameTypeRequiredDescription
usernamestringTwitter username (without @, e.g., "elonmusk")

The same endpoints are available over MCP, and the full machine-readable catalogue lives in the API documentation.

Frequently Asked Questions

Find answers to common questions about Twitter User API

More than just prompts

Supercharge your workflow with AI Automation

Automatio combines the power of AI agents, web automation, and smart integrations to help you accomplish more in less time.

AI Agents
Web Automation
Smart Workflows