API Overview

Introduction

Easy-to-use APIs are provided to technical teams to ensure a smooth event experience for Attendees, Exhibitors, Speakers, Sponsors, and any other visitors.

In this documentation you will find:

Our complete API documentation for use in API integrations

Public API endpoints

Note: This documentation is currently a work in progress, so some sections may still contain gaps or inaccuracies. If you notice anything that seems incorrect, incomplete, or unclear, please reach out to your MICEtribe representative (Customer Success Manager, Project Manager) or contact us at integrations@micetribe.com. We’ll make sure to review and update it as quickly as possible.

API Standard

MICEtribe APIs are RESTful APIs with JSON responses only.

Headers

All API requests must send the following request headers:

Content-Type: application/json

Accept: application/json

Naming Conventions and Versioning

API names will follow camelCase naming conventions.

All APIs should be saved under a specific version, starting with v1.

For example:

/v1/registration

API JSON payloads and response bodies will follow snake_case.

For example:

session_id

Rate Limit

To ensure fair and reliable access for all developers, the MICEtribe API enforces a rate limit of 30 requests per minute.

This limit helps prevent resource overuse and ensures consistent performance for all integrations.

Pagination

Pagination is mandatory for all GET endpoints that return multiple objects in a single response.

Pagination is controlled using the following query parameters:

Page size: Specifies the number of records per page. The maximum is 100.

Page number: Indicates the page number to retrieve. It always starts from 1.

Example:

?page=1&page_size=100

Error Handling

JSON error responses will contain the following attributes:

errors: OBJECT ARRAY — Optional. A hash of each attribute and an array of messages for that attribute.

message: STRING — Always present. Describes the problem.

Example:

{
  "errors": {
    "email": [
      "The email is invalid."
    ]
  },
  "message": "Validation failed."
}

HTTP Status Codes

Status	Description
200 OK	All is well.
401 Unauthorized	Your request is not authenticated.
403 Forbidden	Your request is not authorized because the user has insufficient permissions.
404 Not Found	The endpoint requested does not exist.
422 Unprocessable Entity	The resource couldn't be created or updated due to a validation error. Please see the response body for more information.
429 Too Many Requests	Your application is exceeding its rate limit. Slow down, pal!
500 Internal Server Error	Something is wrong on our end.
502 Bad Gateway	The app responsible for serving your request is temporarily unavailable.
504 Gateway Timeout	Something has timed out on our end.

Environments

Live Environment

Base URL:

https://api.micetribe.com/integrations/v1

Sandbox Environment

Base URL:

https://api.staging.micetribe.com/integrations/v1

Authentication

Authorization

Tokens are generated per event scope. Every new event must have its own generated token.

All API requests must be made over SSL, and API-token-authenticated endpoints MUST only be called from back-end code for security reasons.

Security Notice
API tokens grant access to data in your MICEtribe organization and should be treated like passwords. API tokens should only be shared with trusted parties in a secure manner.

Authorization Scopes

Every generated token will have defined scopes aligned with it. Scopes define the level of access to the event's data.

The API provides granular control over different areas, including:

Registrations

Zones

Analytics

Each area can have Read and Write access.

We highly recommend requesting only the data access your application needs to function.

Security Recommendation
Do not grant full access to everything in your event unless it is required by your integration. Request the minimum permissions necessary for your application.

API Overview

Introduction#

API Standard#

Headers#

Naming Conventions and Versioning#

Rate Limit#

Pagination#

Error Handling#

HTTP Status Codes#

Environments#

Live Environment#

Sandbox Environment#

Authentication#

Authorization#

Authorization Scopes#