Skip to content
/Event

MICEtribe Developers (1.0.1)

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

Download OpenAPI description
index.json
index.yaml
Languages
Servers
Mock server
https://developer.micetribe.com/_mock/apis/
https://developer.micetribe.com/{{base_url}}/

Registration

Operations

Event

Operations

Get Event

Request

Purpose
Retrieve metadata for the active event, including key details (id, slug, name, timezone, start/end) and the available personas with their registration fields. Useful for client apps to configure flows and validate registration inputs.

Endpoint and Method

  • Method: GET

  • URL: {{base_url}}event

Path/URL Variables

  • None. The base URL is parameterized via {{base_url}} in your active environment.

Headers

  • Accept: application/json

  • Accept-Encoding: application/json

Authentication

  • If the API requires auth, use a Bearer token variable. Configure at the folder/collection level or request level:

    • Type: Bearer Token

    • Token: {{token}}

  • If auth is inherited from the collection/folder, no per-request changes are needed here.

Sample Success Response (200) — summarized
{ "event_id": 6200,

"slug": "mobapp",

"name": "vFairs Mobile app integration",

"timezone": "Asia/Qatar",

"start_date": "2025-11-09T10:00:00+03:00",

"end_date": "2025-11-30T22:00:00+03:00",

"personas": [ {

"id": 15910, "slug": "visitor", "name": "Visitor",

"fields": [ { "id": 323339, "slug": "fullname", "label": "Full name", "type": "Name" }, { "id": 323340, "slug": "email", "label": "E-mail", "type": "E-mail" }, { "id": 323341, "slug": "phone", "label": "Phone number", "type": "Phone number" }

] }, // Additional personas such as exhibitor, speaker, vip, media, etc. ] }

Key fields: event_id, slug, name, timezone, start_date, end_date. Personas is an array; each persona has id, slug, name, and fields[]. A field has id, slug, label, type, and optional values (e.g., radio options).

Response Codes

  • 200 OK: Event metadata returned successfully.

  • 400 Bad Request: Invalid query parameter(s).

  • 401 Unauthorized: Missing/invalid token when authentication is enforced.

  • 404 Not Found: Event not available.

  • 5xx Server Error: Unexpected server-side issue.

Usage Tips (Environments and Variables)

  • Set {{base_url}} in your active environment (e.g., Sandbox) to target the appropriate host.

  • Store {{token}} in the same environment and configure Authorization to inherit Bearer token.

  • Use examples above for query parameters; toggle them in the Params tab as needed.

  • Do not modify method, URL, or headers when using this request unless your API variant requires it.

Security
BearerAuth
Headers
Accept-Encodingany
Example: application/json
Bodyapplication/json
object
curl -i -X GET \
  https://developer.micetribe.com/_mock/apis/event \
  -H 'Accept-Encoding: application/json' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{}'

Responses

event

Headers
Datestring
Example: "Mon, 22 Dec 2025 13:36:53 GMT"
Transfer-Encodingstring
Example: "chunked"
Connectionstring
Example: "keep-alive"
Serverstring
Example: "nginx/1.18.0 (Ubuntu)"
Cache-Controlstring
Example: "no-cache, private"
X-Ratelimit-Limitinteger
Example: "30"
X-Ratelimit-Remaininginteger
Example: "29"
Access-Control-Allow-Credentialsboolean
Example: "true"
Access-Control-Allow-Methodsstring
Example: "GET, PUT, POST, DELETE, PATCH, HEAD, OPTIONS"
Access-Control-Allow-Headersstring
Example: "*"
Access-Control-Expose-Headersstring
Example: "*"
All rights reserved for MICEtribe.