The API has been designed to provide a detailed and structured view of each post, making it an essential tool for users who want to understand and optimize their social media presence.
Upon receiving a tweet ID or associated data, the API returns a complete set of metrics and attributes. These include the tweet text, creation date, language, content sensitivity, and display range. It also provides comprehensive user information such as name, username, verification, profile picture, and additional features that help to better contextualize the origin of the message.
One of the most relevant aspects is engagement metrics, such as the number of likes, retweets, replies, quotes, and views, which are essential indicators for measuring the impact of a post. The API also provides details on associated conversations, the number of comments, and whether the tweet is part of a thread, allowing for a more in-depth analysis of user interaction.
The API also manages embedded media information, such as photos and videos, delivering URLs in different formats, resolutions, and metadata, which expands the possibilities for visual content analysis. All of this is complemented by structured data on hashtags, mentions, and links, which are key to understanding the spread of the message and its reach within the network.
Analyzes individual tweets, returning text, user, interaction metrics, media, and conversational context, ideal for social monitoring and digital analysis.
{"Example Response":"No response example available for now."}
curl --location --request GET 'https://zylalabs.com/api/10351/capture+tweet+metrics+api/19905/tweet+fetcher&tweet_id=Required' --header 'Authorization: Bearer YOUR_API_KEY'
Get complete details about a tweet, including text, user, engagement metrics, attached media, and conversational context on social media.
{"Example Response":"No response example available for now."}
curl --location --request GET 'https://zylalabs.com/api/10351/capture+tweet+metrics+api/19909/tweet+analytics&tweet_id=Required' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The GET Tweet Fetcher returns tweet text, user information, engagement metrics, media details, and conversational context. The GET Tweet Analytics provides a comprehensive overview, including all the same data plus additional insights into user interactions and content performance.
Key fields include tweet text, creation date, user name and username, engagement metrics (likes, retweets, replies), media URLs, and conversation details. These fields help analyze tweet performance and user engagement.
The response data is structured in JSON format, with nested objects for user information, engagement metrics, and media details. This organization allows for easy parsing and integration into applications for further analysis.
Users can specify parameters such as tweet ID for the GET Tweet Fetcher and additional filters like date range or engagement metrics for the GET Tweet Analytics. These parameters help tailor the data returned to specific needs.
Typical use cases include social media monitoring, content strategy optimization, and performance analysis of tweets. Marketers and analysts can leverage the metrics to enhance engagement and refine messaging strategies.
Data accuracy is maintained through direct integration with Twitter's API, ensuring real-time access to tweet metrics. Regular updates and validation checks help ensure the reliability of the data provided.
Users can analyze engagement metrics to identify high-performing content, track user interactions for sentiment analysis, and assess media effectiveness. This data can inform future content strategies and audience targeting.
Users can expect consistent data patterns, such as engagement metrics correlating with tweet reach and user interactions. Analyzing these patterns helps identify trends and optimize future tweet performance.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
56ms
Service Level:
100%
Response Time:
396ms
Service Level:
100%
Response Time:
400ms
Service Level:
100%
Response Time:
21ms
Service Level:
100%
Response Time:
19ms
Service Level:
100%
Response Time:
636ms
Service Level:
100%
Response Time:
499ms
Service Level:
100%
Response Time:
4,625ms
Service Level:
100%
Response Time:
1,037ms
Service Level:
100%
Response Time:
774ms
Service Level:
100%
Response Time:
9,118ms
Service Level:
100%
Response Time:
72ms
Service Level:
100%
Response Time:
53ms
Service Level:
100%
Response Time:
57ms
Service Level:
100%
Response Time:
13,346ms
Service Level:
100%
Response Time:
53ms
Service Level:
100%
Response Time:
1,718ms
Service Level:
100%
Response Time:
991ms
Service Level:
100%
Response Time:
15ms
Service Level:
100%
Response Time:
58ms