ExpoPlatform Open API V2
The Open API V2 is ExpoPlatform's public REST API for programmatically managing event data. It lets you and your integration partners create, read, update, and delete the core entities that make up an event — participants, exhibitors, sessions, products, floor plan, meetings, news, and notifications — without manual work in the platform back-office.
This space is the home for everything related to the Open API V2: a plain-language Introduction, a full endpoint reference for every section, and how-to guides for the most common integration tasks.
The big picture
A few concepts are worth understanding before you begin:
-
Environment-based architecture. Each client has a single data environment (one shared database) that hosts all of their events. Some data is global (shared across every event); some is local (specific to one event). Understanding this distinction is essential before writing any integration — it is covered in detail in the Introduction.
-
Consistent request and response format. Most write operations use
multipart/form-dataand return a consistent JSON envelope. Many endpoints operate as upserts (create-or-update). -
IDs come from GET endpoints. Most write operations depend on internal IDs retrieved from corresponding GET endpoints. The how-to guides make these dependencies explicit.
-
Authentication via API key. Every request carries a Bearer API key scoped to a specific account.
How to use this documentation
|
If you want to… |
Go to… |
|---|---|
|
Understand the API, the data model, and key conventions |
Introduction |
|
Look up a specific endpoint's parameters and responses |
The relevant section (Accounts, Sessions, Exhibitors, etc.) |
|
Follow step-by-step instructions for a task |
The how-to guides under each endpoint |
Swagger / OpenAPI reference
The complete machine-readable specification — every endpoint, parameter, and schema — is available in the interactive Swagger documentation:
Swagger documentation: https://api-newdemo.expoplatform.com/apidocs/v2/swagger.html
Use the Swagger reference for the authoritative parameter list and to try requests interactively. Use this documentation space for guidance, context, and worked examples that the raw specification does not provide.