Introduction#
The GET Eventportal API allows external partners to integrate the GET Eventportal into their web and app platforms. It supports end-user interactions, enabling functionalities such as linking chips or tickets, retrieving wallets and transactions, displaying balances and overviews, as well as showcasing the shop and payout flow.Authentication Flows#
To access API funcionalities, you need to obtain an entityToken. We support two primary flows for this. Detailed sequence diagrams for both flows are available here, illustrating their respective call sequence.1.
User login with event promoter specific SSO (login flow): AppApiV1UserData
If your event is using an dedicated SSO integration with GET, you can exchange the SSO id token to a GET Eventportal API specific userToken that can be used to list, add and remove wallets. You don’t have to store entityTokens on your end as those are issued for the linked wallets of the user. 2.
Flow without user login (anoymous flow): AppApiV1Token
If your event does not have dedicated SSO integration with GET, you can obtain entityTokens without user connection. You have to take care of storing those tokens within your user space. Once you have obtained an entityToken using one of the above flows, you can:Fetch the overview data (e.g. balance).
Retrieve list of transactions.
Access widget URLs to display shop, payout and hosted overview.
Modified at 2025-04-04 13:16:47