Analytics API
Download the raw analytics data of your events: every page view, meeting, message, connection and bookmark, one action per line.
What you can do
| Use case | Start with |
|---|---|
| Export all user actions for an event and a time range | Export analytics data |
| Track page views, searches and session video streams | Page views |
| Measure meeting requests and meetings | Meetings |
| Measure networking: connections and connection requests | Connections |
| Count chat messages and video calls | Chat |
| See which exhibitors, sessions and products users bookmark | Bookmarks |
Endpoint
Unlike the Content API, the Analytics API is not a GraphQL API. It has a single HTTP endpoint, and every export is a POST to:
https://developer.swapcard.com/event-admin/export/analytics
How the export works
- You send a JSON body with the IDs of your events and a time range (
time_gtandtime_lt, both required). - The response is a stream of newline-separated JSON objects, ordered from the least to the most recent.
- Each JSON object is one action a user performed on the platform, such as viewing an exhibitor or accepting a meeting.
- Each object contains a
cursor. Send it in your next request to retrieve all the actions that come after it. - Without a
limit, the stream is potentially infinite.
See Export analytics data for the full request and response reference.
Authentication
Send an API key created in Swapcard Studio in the Authorization header. See Authentication.
Get started
- Make your first export: follow Export analytics data.
- Find an action name: browse the action types, starting with Page views.
- Questions about the numbers? Read the Analytics API FAQ.
Limits and versioning
- Data is delayed by 10 minutes, and the time range filters affect performance. See Limits and data delay.
- Changes to the API are announced in the Changelog and follow the versioning and deprecation policy.