Overview

Eventpop Public API 0.0.1

Integrate with Eventpop to build event management tools, ticket validation apps, and user experiences. Supports OAuth 2.0.

Tokens

Every operation lists the token it accepts in security.

User token (user_token): the authorization code grant. It acts for one user. The public scope reads the user’s own data. The organizer scope acts for an organizer team that the user belongs to.
Application token (application_token): the client credentials grant. It acts for the organizer that owns the application.

Organizer apps and `super_app`

An organizer’s own app is not a super_app. In the buyer endpoints, organizer_id must be the organizer that owns the app. This is the wall that stops the app from reading what the user bought from another organizer.
A super_app skips the consent screen and this wall. It can use any organizer_id.
GET /me/organizers lists the organizer teams that the user belongs to. It does not list the organizers that the user bought from. An organizer’s own app sees only its owner organizer.

Eventpop Developer Team

https://docs.eventpop.me

Information

OpenAPI version: 2.0

Authentication

user_token

Security scheme type: oauth2

Flow type: accessCode

Authorization URL: https://www.eventpop.me/oauth/authorize

Token URL: https://www.eventpop.me/oauth/token

Scopes:

public - Access user profile and user-owned resources (orders, tickets)
organizer - Access organizer resources, check-in and ticket management (requires user-organizer association)

application_token

Security scheme type: oauth2

Flow type: application

Token URL: https://www.eventpop.me/oauth/token

Scopes:

public - Read the events and tickets of the organizer that owns the application