After Creating a Report¶
Once you’ve created a report using the Tweet Binder API, you can monitor its status and perform several actions to retrieve data and statistics.
Report Statuses¶
Every X (Twitter) Listening report goes through a series of statuses during its lifecycle:
-
waiting
The report has been created but is still collecting its first tweets. This usually happens right after creation. -
generated
The report has finished processing and is ready. All available statistics can now be retrieved. -
outdated
(only for live reports)
The report is currently being updated. This is common for live tracking reports. - The time it remains in this state depends on how many tweets have been collected.
- More tweets = longer update time.
➡️ To check the current status of your report, use the endpoint:
Fetch a Report
This will return a status
property that shows the current state.
What Can You Do with the Reports?¶
Once the report status is generated
, several actions become available:
1. Get Report Statistics¶
Use the following endpoint to fetch all available statistics:
Get Report Stats
This includes aggregated data such as:
- Number of tweets
- Top users
- Hashtag analysis
- Device breakdown
- Activity timeline
- And more
2. Perform Report Actions¶
Tweet Binder reports support multiple API actions that allow you to interact with or modify the report.
See the full list of supported actions here:
Report Actions
Some of the most useful actions include:
- Updating a live report
- Cloning a report
- Refreshing engagement data
3. Get Report Content¶
If you need access to the actual tweet data collected in the report, use this endpoint:
Get Report Content
This action returns the full list of post ids (tweets) or user ids that were gathered for your query.
Summary¶
After creating a report:
- Monitor its status (
waiting
,generated
,outdated
) - Use the appropriate actions to:
- View statistics
- Access raw tweet data
- Perform updates or maintenance
All endpoints related to reports can be found in the Report Actions section of the documentation.