Reporting endpoint - Ticket status logs
Overview
This endpoint exposes the TIXNGO ticket status logs stored in the Reporting Domain.
It enables you to:
Analyze spectators’ ticket transfer activity (incoming and outgoing transfers)
Focus on specific actions to understand user behavior
Be mindful of the volume of data involved! Please try to focus on date range as short as possible.
If you have significant volume of data to analyze, Excel and Power BI desktop are NOT the right tools. In those contexts, direct API integration or Power BI services with incremental refresh activated MUST be used.
Endpoint
The endpoint to fetch ticket status logs is:
GET /organizer/report/ticket-status-logsParameters
Required
mobileAppId (string)
Identifier of the mobile application for which you want to retrieve logs.
from (date‑time)
Start of the date‑time range for which logs are returned.to (date‑time)
End of the date‑time range for which logs are returned.
Using a mandatory date range prevents dumping millions of records for large organizers.
Optional filters
actionNames (string, multiple values supported)
Filter by action type (for example:Download,Activate,Log off, …).fromStatuses (string, multiple values supported)
Filter by initial ticket status before the action.toStatuses (string, multiple values supported)
Filter by ticket status after the action.fromOwnerId (string)
Filter by previous ticket owner.toOwnerId (string)
Filter by new / current ticket owner.actor (string)
Filter by actor that performed the action (for example: mobile device, back‑office user, …).
Pagination
limit (integer, optional; default as configured, max 10 000)
Maximum number of items returned in one page.
The maximum allowed value is 10 000.paginationKey (string, optional) If not provided, the first page of results is returned. Use the nextPageKey from the previous response to get the next page.
Data returned
pagination |
| ||||||||||||||||||||||||||||||||||||||||||||||||||
result | List of ticket status log entries
|