API for lists timeline

You need to ship a “lists-like” timeline view this week—show a user’s profile, pull a clean replies feed, and enrich it with who they follow. By the end of this article, you’ll know the exact endpoints to call on Zyla API Hub’s Twitter Data All-in-One API to fetch a user profile, retrieve their replies timeline, and enumerate who they follow—enough to render a compact, skim-friendly timeline component in your app.

What this API delivers and when to use it

The Twitter Data All-in-One API returns structured data for public Twitter accounts. With the endpoints covered here you can:

• Resolve a profile by screen name, including status, avatar, header image, and counts.
• Retrieve detailed “about profile” metadata such as verification, affiliate label, and origin info.
• List the accounts a user follows to seed people-based feeds.
• Fetch the user’s replies timeline (a practical stand-in for a “lists timeline” when you want focused, conversational content).

These pieces are commonly used to power user cards, detail views, and timeline panes in dashboards, CRM-sidebars, research tools, and internal monitoring consoles.

Getting started on Zyla API Hub

Zyla API Hub centralizes more than 10,000 public APIs behind one account, one key, and one subscription model. Open the API’s page, subscribe, and use your key across the listed endpoints.

1. Open Zyla API Hub and find the Twitter Data All-in-One API page (link in the CTA below). Zyla’s catalog is browsable at zylalabs.com.
2. Click Subscribe (or Start Free Trial when available) to generate your API key.
3. Send requests with Authorization: Bearer YOUR_API_KEY to the Hub URLs below.

Billing is subscription + quota (not pay-per-call). For the first API, you can expect a 7-day trial or 50 requests—check the API page for current access options and pricing. There is no Free Plan.

Endpoints you’ll use

Below are the publicly documented Hub URLs, HTTP methods, and the required parameters exactly as provided. All requests use the header Authorization: Bearer YOUR_API_KEY. Do not add extra parameters.

1) Profile

• Method: GET
• URL: https://zylalabs.com/api/3399/twitter-data-all-in-one-api/3673/profile
• Required query param: screenname (string)
• Purpose: Returns core profile data (status, avatar, header image, counts, and metadata).

Official example (copy verbatim):

curl -s -X GET "https://zylalabs.com/api/3399/twitter-data-all-in-one-api/3673/profile?screenname=elonmusk" \
-H "Authorization: Bearer YOUR_API_KEY"

Official JSON response:

{
"status": "active",
"profile": "MikeCiesla",
"rest_id": "23880336",
"blue_verified": true,
"affiliates": [],
"business_account": [],
"avatar": "https://pbs.twimg.com/profile_images/1699329166234247168/G1W8YKJy_normal.jpg",
"header_image": "https://pbs.twimg.com/profile_banners/23880336/1695301088",
"desc": "Web3 at Google Cloud",
"name": "MikeCiesla",
"protected": null,
"location": "🦘🇦🇺",
"friends": 969,
"sub_count": 219,
"statuses_count": 48,
"media_count": 2,
"pinned_tweet_ids_str": [],
"created_at": "Thu Mar 12 02:45:15 +0000 2009",
"id": "23880336"
}

What you’ll likely use immediately:

• status: account status at fetch time.
• rest_id and id: internal identifiers you can store for joins.
• avatar, header_image, name, desc, location: for rendering profile cards.
• friends, sub_count, statuses_count, media_count: stats for badges/counters.
• created_at: an RFC822-like timestamp with UTC offset (+0000).

2) About profile

• Method: GET
• URL: https://zylalabs.com/api/3399/twitter-data-all-in-one-api/22582/about-profile
• Required query param: screenname (string)
• Purpose: Returns additional verification, affiliation, and “about” metadata for the profile.

This endpoint is useful when you need verified/badge info and origin details to complement the core profile response.

3) Following

• Method: GET
• URL: https://zylalabs.com/api/3399/twitter-data-all-in-one-api/3679/following
• Required query param: screenname (string)
• Purpose: Returns the list of accounts the user is following, with key counts and profile info.

Use this to construct “people to follow” sections, tune your timeline to followed accounts, or build allowlists for filtering a replies feed.

4) User replies

• Method: GET
• URL: https://zylalabs.com/api/3399/twitter-data-all-in-one-api/3682/user-replies
• Required query param: screenname (string)
• Purpose: Returns a list of the user’s replies (a focused, conversation-heavy timeline).

For developers looking to ship a “lists timeline” experience centered on selective discussion rather than a full firehose, a replies timeline is a practical alternative: a smaller, more relevant feed for embedding next to analytics, support tickets, or CRM records.

One working request you can run now

Here is the official profile fetch you can paste into your terminal. It uses the Profile endpoint and the Authorization header:

Python example: render a compact profile card

This Python snippet calls the same Profile endpoint, reads the fields you actually render, and prints a summary you can drop into logs or templates.

import os
import requests

API_KEY = os.getenv("ZYLALABS_API_KEY", "YOUR_API_KEY")
SCREENNAME = "elonmusk"
URL = "https://zylalabs.com/api/3399/twitter-data-all-in-one-api/3673/profile"

resp = requests.get(
URL,
params={"screenname": SCREENNAME},
headers={"Authorization": f"Bearer {API_KEY}"}
)
resp.raise_for_status()
data = resp.json()

card = {
"status": data.get("status"),
"id": data.get("id"),
"rest_id": data.get("rest_id"),
"name": data.get("name"),
"handle": data.get("profile"),
"avatar": data.get("avatar"),
"header_image": data.get("header_image"),
"desc": data.get("desc"),
"location": data.get("location"),
"counts": {
"friends": data.get("friends"),
"subscribers": data.get("sub_count"),
"statuses": data.get("statuses_count"),
"media": data.get("media_count"),
},
"created_at": data.get("created_at")
}

print("Profile card:")
for k, v in card.items():
print(f"- {k}: {v}")

Understanding responses you’ll parse

About profile

When you call About profile with a screen name, you’ll receive detailed metadata including verification, affiliates, and the “about” section. Exact example:

Fields you’ll use:

• blue_verified: boolean for badge rendering.
• affiliates.label.badge.url and affiliates.label.description: show an org badge next to the name.
• about.account_based_in, about.source: contextual tooltips on profile origins.

Following

The Following endpoint returns an array of lightweight user objects the profile follows. Exact example:

Fields to note:

• following: array of accounts with counts suitable for chips/cards.
• more_users: if true, you should plan for pagination or subsequent fetches.

User replies

The User replies endpoint returns a conversation-centric timeline for the user. Exact example (truncated as provided):

{"timeline":[{"tweet_id":"1867196702865674450","bookmarks":0,"created_at":"Thu Dec 12 13:15:59 +0000 2024","favorites":0,"text":"RT @cb_doge: Every citizen journalist who fought the legacy media narrative and spread the truth this election is the Person of the Year.…","lang":"en","in_reply_to_status_id_str":null,"views":null,"quotes":0,"replies":0,"retweets":10,"conversation_id":"1867196702865674450","media":[],"entities":{"user_mentions":[{"id_str":"1389913567671975937","name":"DogeDesigner","screen_name":"cb_doge"}],"urls":[],"hashtags":[],"symbols":[]},"author":{"rest_id":"44196397","name":"Elon Musk","screen_name":"elonmusk","followers_count":207267106,"favourites_count":99802,"avatar":"https:\/\/pbs.twimg.com\/profile_images\/1858316737780781056\/kPL61o0F_normal.jpg","blue_verified":true},"retweeted":{"id":"1867196122143563838"},"retweeted_tweet":{"tweet_id":"1867196122143563838","bookmarks":0,"created_at":"Thu Dec 12 13:13:41 +0000 2024","favorites":119,"text":"Every citizen journalist who fought the legacy media narrative and spread the truth this election is the Person of the Year. \n\n https:\/\/t.co\/B8boPofzKx","lang":"en","quotes":2,"replies":60,"retweets":10,"conv…

Implementation notes:

• created_at is an RFC822-like timestamp with UTC offset (+0000). Normalize to UTC or ISO 8601 in your service layer if needed.
• entities contain standard URL, mention, and hashtag objects for autolinking.
• retweeted and retweeted_tweet appear when the item is a retweet; check both text and nested objects to render consistently.

How to compose a “lists timeline” from these pieces

While no dedicated “lists timeline” endpoint is documented here, you can assemble a focused, list-like feed by combining the following:

1. Fetch Following to build a set of accounts of interest for your user.
2. Fetch User replies to surface conversational items from that user—often the most relevant signal for monitoring.
3. Join with Profile/About profile for badges and context (blue_verified, affiliate badge) to render trust and source details inline.

This approach is practical for dashboards where you want a compact, discussion-first view rather than a full home timeline. Cache profile and following results for several minutes to avoid repeated metadata fetches; keep the replies fetch fresh if you display near-real-time activity.

Production notes that save time

• Auth: Every request must include Authorization: Bearer YOUR_API_KEY.
• Time handling: created_at fields include a +0000 offset—treat as UTC. Convert once at fetch time and store as a datetime in your DB.
• Pagination: If more_users appears on Following, plan for follow-up fetches. If a timeline endpoint indicates truncation in your UI, add a “Load more” even if not shown in the excerpt.
• Caching: Profile and About profile change less frequently. Cache them separately from replies or other timelines.
• Quotas: The Hub uses subscription + quota. For the first API, expect a 7-day trial or 50 requests; don’t hardcode limits—check the item page.

Call these APIs from an AI agent via MCP

If you are wiring this into an AI coding agent (Claude Code, Cursor, Windsurf or any MCP-compatible client), point it at the MCP endpoint and pass your Zyla key in the URL:

https://mcp.zylalabs.com/mcp?apikey=YOUR_API_KEY

Use your agent’s MCP configuration to expose HTTP tools and route calls to the Hub URLs in this article. For reference, see MCP. This lets an agent read profiles, fetch replies, and iterate on transformations without you hand-writing every request.

Endpoint reference: exact request URLs and parameters

• GET https://zylalabs.com/api/3399/twitter-data-all-in-one-api/3673/profile
  • Params: screenname (string, required)
• GET https://zylalabs.com/api/3399/twitter-data-all-in-one-api/22582/about-profile
  • Params: screenname (string, required)
• GET https://zylalabs.com/api/3399/twitter-data-all-in-one-api/3679/following
  • Params: screenname (string, required)
• GET https://zylalabs.com/api/3399/twitter-data-all-in-one-api/3682/user-replies
  • Params: screenname (string, required)

Putting it together: minimal flow for a “lists-like” panel

1. On profile load: call Profile (for avatar, counts) and About profile (for verified and affiliate badge).
2. Prefetch Following and cache for short intervals (e.g., 10–30 minutes) to power filter chips or people lists.
3. Render User replies in a scrolling pane. Use entities to autolink mentions and URLs. If you detect retweeted_tweet, display the nested text and counts.
4. Store rest_id/id for joins so you don’t depend on screen name changes.

You can always return to the Zyla API Hub catalog to add more capabilities to this view later; one account and key cover the marketplace at zylalabs.com.

FAQ

How do I authenticate?
Send the header Authorization: Bearer YOUR_API_KEY with every request to the Hub URLs shown above.

Which timestamp format do replies use?
created_at is an RFC822-like string including a UTC offset (e.g., Thu Dec 12 13:15:59 +0000 2024). Normalize to UTC or ISO 8601 before storage.

Is there a dedicated “lists timeline” endpoint?
Not in the endpoints listed here. You can approximate a lists-style view by combining Following with User replies and enriching with Profile/About profile metadata.

What are the current quotas and pricing?
Zyla uses subscription + quota (not pay-per-call). For the first API, expect a 7-day trial or 50 requests. Check the API page for current access options and pricing.

Can I call these endpoints from an AI agent?
Yes. Use the MCP endpoint https://mcp.zylalabs.com/mcp?apikey=YOUR_API_KEY in your MCP-compatible client and route requests to the Hub URLs from within the agent’s tool calls.

Start 7-day trial on Twitter Data All-in-One API to get your key and ship your timeline integration. One account, one key, thousands of APIs on Zyla.