TikHub’s X profile endpoint, called directly
Direct
GET /apis/v1/tikhub/twitter/web/fetch_user_profile?screen_name=…Source 1 of 2 · 954 endpoints across 25 platformsListed in the catalog as twitter fetch_user_profile
UnifiedSoon
You get TikHub’s own JSON here, and your code depends on it. social.accounts.get returns the same account as an Account and can switch sources for you. Use the Unified call
curl "https://api.aisa.one/apis/v1/tikhub/twitter/web/fetch_user_profile\ ?screen_name=acme_robotics" \ -H "Authorization: Bearer $AISA_API_KEY"
Calling this path always uses TikHub. Metered per call: TikHub’s price plus AIsa’s published fee.
- Starting price
- $0.001 · metered
- How it's priced
- cost × multiplier
- Success · 30 days
- Not measured yet
- Median latency
- Not measured yet
Inputs
screen_namestringone ofThe handle, without the @.rest_idstringone ofThe numeric X user ID, when you already have it.
The catalog has no parameter list for this endpoint yet. These two come from TikHub's own reference.
Limits & cost
- Pricing
- Metered: provider cost × multiplier. $0.001 is a representative starting price.
- Empty answer
- Not yet published
- Constraints
- None listed in the catalog yet
- Cost note
- No cost note for this endpoint yet
- Rate limit
- Not yet published
Sample call
GET /apis/v1/tikhub/twitter/web/fetch_user_profile
?screen_name=acme_robotics
200 · $0.001 · TikHub's own JSON, abridged
{
"code": 200,
"data": {
"[TikHub's user object]": {
"screen_name": "acme_robotics",
"name": "Acme Robotics",
"followers_count": 48210,
"...": "fields exactly as TikHub returns them"
}
}
}