Using the Events API
The Events API is a programmatic method to access data of events, sessions, session tracks, passes, speakers, and sponsorships. Additionally, it allows you to register for events and sessions.
The API access is over HTTPS protocol and is accessed from the API endpoint that you receive while creating a web application token. All data is sent and received as JSON.
Blank fields are included as
null instead of being omitted.
Every customer has their own endpoint URL. The Event API endpoint URL consists of two parts:
- The endpoint domain
- The subdirectory
You will get the root endpoint after creating a web application token. You can find more information on how to create a web application token here: Register web application.
Example for root endpoint
The subdirectory always starts with
EvtMgmt/api followed by the API version (which can be retrieved from the API documentation available here: Event management API reference docs.
Example for subdirectory
Example for full endpoint URL
To use the Events API, you need to provide a
web application token as a URL parameter in each request. The web application token is used to control API requests that are associated with your organization. See Register web application for more information on how to create and retrieve a web application.
web application token can be added to the request by adding a URL parameter called
Additionally, the origin from where the request is sent must be equal to the origin specified when creating the web application token.
If you do not provide a web application token or the Origin Header, the Events API will return
HTTP 400 Bad Request.
If the web application token is invalid, the Events API will return
HTTP 401 Unauthorized.
Register your web application
To use the Events API, you need to provide a web application token in each request. The web application token is used to control API requests that are associated with your organization. More information: Register your web application