A Twitter Data API returns a public X profile as JSON from a screenname — no scraper. On Zyla API Hub that listing is id 3399, Twitter Data All-in-One API. The Profile path is GET /api/3399/twitter-data-all-in-one-api/3673/profile. Official docs example: screenname=elonmusk.
The Hub catalog is more than 10,000 public APIs. You subscribe per API (monthly or annual, with an included quota). There is no Free Plan. Your first Hub API includes a 7-day free trial (up to 50 requests). Failed quality-monitored listings are discontinued; first-level support intermediates with the provider.
Use cases
- CRM enrichment. Store the official handle and hydrate display name, bio, and follower counts on a lead record.
- Watchlist. Re-fetch a fixed list of screennames on a schedule and alert when the bio or username changes.
- Research queue. Resolve a handle first, then call Timeline or Search on the same listing with the same Hub key.
Profile: official screenname example
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://zylalabs.com/api/3399/twitter-data-all-in-one-api/3673/profile?screenname=elonmusk"
screenname is required. Copy the live JSON from your key — this article does not invent a profile payload.
Same listing: Tweet and Search
Official Tweet example id: 1748428323548758414.
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://zylalabs.com/api/3399/twitter-data-all-in-one-api/3675/tweet?id=1748428323548758414"
Search requires query, search_type (Top / Latest / People / Lists), and a cursor from the previous page (next_cursor / prev_cursor). Official query sample: elon musk with search_type=Latest.
Go live
1. Register — 7-day trial on the first Hub API (or 50 requests).
2. Subscribe on the item page.
3. GET Profile with screenname.
4. Reuse the same key for Tweet, Timeline, and Search.
Is Hub billing pay-per-call?
No. Hub billing is a subscription plus quota per API. MCP call_api uses that same subscription if you connect https://mcp.zylalabs.com/mcp.
