Reporting endpoint - Spectator Details

Overview

Organizers can now easily export all spectator data for analytics, compliance, and operational needs. This report is generated for all spectators to provide a detailed of spectator details and it could scale to 5 millions of records and support near real-time reporting.

This is only available to organizers using Spectator V4. See Spectator V4for more information.

Parameters

mobileAppId (required): specify the applicable application identifier

limit (required): maximum number of results to extract

paginationKey (optional): if not provided, the system will return the first page. Use the nextPageKey from the previous call to get the next page.

lastUpdatedSince (optional): Filter data

lastUpdatedBefore (optional): Filter data updated before the given timestamp

Data returned

pagination

pageSize

integer

Total number of spectator of this page

nextPageKey

string

Designed for the pagination

result

List of spectators

spectatorId	string Spectator ID
firstName	string First Name
lastName	string Last Name
email	string Email
communicationLanguage	string Communication Language
locked	boolean Spectator is locked or not
status	string Spectator’s status (ACTIVE, INACTIVE, LOCKED,…)
acquiredBy	string Why spectator has been initially created (INJECTION, TRANSFER, REGISTRATION) https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/339411699/Manage+and+protect+spectators+data#Acquired-by
referredBy	string first user referred this app to initial spectator. https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/339411699/Manage+and+protect+spectators+data#Referred-by
ssoClaim	JSONB Stores all SSO claims as JSON
createdAt	string($date) Date of spectator’s account creation
updatedAt	string($date-time) Date of spectator’s account last updated