XpoBay
Sign inBook a demo
PRIVATE API ACCESS

Connect XpoBay without publishing the playbook.

Approved clients can use the XpoBay API to connect agreed event and participant workflows with the systems they already rely on.

API documentation, request schemas, credentials and implementation guidance are supplied privately after the required workflow and access have been agreed. They are not published on the public website.

Request API access →Explore integrations
Controlled access for approved clients
client-api-access
ACCESS STATUS

Documentation   Private
Credentials     Client-specific
Scope           Agreed workflow
Guidance        Supplied by XpoBay
→
✓Approved accessIntegration pack
DocsCredentials
Supplied on request
02

Start with the outcome, not the endpoint.

Every integration begins with the operational result the organiser needs. XpoBay then confirms the appropriate route, available capabilities and implementation scope.

Common integration outcomes

  • Create or update participant records from a CRM, registration platform or internal system
  • Supply the User Types, User Categories and stand information needed to personalise each Workspace
  • Keep selected participant information current across connected systems
  • Support agreed onboarding and welcome-email workflows
  • Publish approved profile content to event websites or show apps through event-specific feeds

The precise fields, operations and update rules are confirmed against the current API and the agreed client workflow.

Connect the systems that already hold the data
Create and maintain users
CRM
→
Private API
→
XpoBay
→
Workspace
Publish approved content
XpoBay
→
JSON / XML
→
Website
+
Show app
03

Documentation is supplied after access is approved.

We do not publish a general endpoint catalogue or downloadable credentials. The technical material supplied to each client is limited to the integration being planned and the people authorised to deliver it.

The access process

  1. Define the source system, intended workflow and data that needs to move
  2. Confirm responsibilities, scope, security requirements and implementation approach
  3. Receive the relevant documentation, authentication details and examples privately
  4. Test the agreed workflow before production launch
A controlled route from request to launch
Access review
Source systemData flowAuthorised teamSecurity
After approval

Private integration pack

Relevant documentation, credentials, examples and test guidance.

Only what the agreed implementation needs.
04

Access stays tied to the client and the agreed implementation.

API documentation and credentials are confidential implementation materials. They should be shared only with the client team and any implementation partner specifically authorised to work on the connection.

Before production access

  • The client and authorised delivery contacts are identified
  • The integration purpose and data flow are agreed
  • Credentials are stored and handled securely
  • Testing and error handling are completed
  • Material changes are coordinated with XpoBay
The right access for the right delivery team
X
Approved integrationClient-specific access
ClientAuthorised partnerXpoBay
✓

Controlled delivery

01Agreed scopeDefined data and workflowConfirmed
02Private credentialsHandled by authorised contactsProtected
03Test before launchErrors and update rules checkedRequired
05

Use the API and event feeds for different jobs.

The private API supports approved operational integrations, such as moving participant and event information between XpoBay and another system.

Event-specific JSON or XML feeds are used to make selected, approved profile content available to an event website or show app. Keeping these routes separate makes the implementation easier to control and support.

Two routes. Two clear purposes.
Operational data
Client system
→
Private API
→
XpoBay
Approved published content
XpoBay
→
Event feed
→
Website / app
06

Tell us what needs to connect.

Share the system you want to connect, the events and users involved, the direction in which information needs to move and the workflow you are trying to remove.

We will confirm whether the API, an event feed, spreadsheet import or another supported route is the most practical approach.

Request API access →Explore integrations
Begin with the workflow
INTEGRATION REQUEST

What needs to move?

Source systemEvent dataUpdate rules
Clear route to launch
1Describe the workflowSystem, users and data flow
2Confirm the approachAPI, feed or import
3Receive approved accessDocumentation supplied privately
QUESTIONS

API access FAQ

Clear answers about private documentation, authorised access and implementation planning.

Is the XpoBay API documentation public?+

No. Documentation, schemas, examples and credentials are supplied privately to approved clients and authorised implementation partners for an agreed integration.

Who can request API access?+

A current or prospective XpoBay client can discuss API access. An external implementation partner may be included where the client authorises them and the proposed access is agreed with XpoBay.

What information should we provide?+

Tell us which system will connect to XpoBay, which events and users are involved, what data needs to move, the direction and frequency of updates, and the operational outcome required.

Are event feeds the same as API access?+

No. Event feeds publish selected approved content from XpoBay to a website or show app. API access is considered separately for approved operational integrations.

CONTROLLED CONNECTIONS

Connect the systems that matter without exposing the implementation.

Define the workflow with us and receive the technical access your approved project requires.

Request API access →Explore integrations