# MICEtribe Developers Easy-to-use APIs are provided to technical teams to ensure smooth event experiece for Attendees, Exhibitors, Speakers, Sponsors and any other visitor. Version: 1.0.1 ## Servers ``` {{base_url}} ``` ## Security ### BearerAuth Type: http Scheme: bearer ## Download OpenAPI description [MICEtribe Developers](https://developer.micetribe.com/_bundle/apis/index.yaml) ## Registration ### Create/Update Registration - [POST /registration](https://developer.micetribe.com/apis/registration/paths/~1registration/post.md): You can use reigstration api to create or update registrations on any persona on your event. Same API is used to create indivisual and group registration. First, you need to create persona on MICEtribe event and add all fileds along with their settings then you can use the API to push to your event. Create registration API require the following params: - persona: it's required param to pass to the API. It is the slug of the persona you want to push to. - fields: it's required param to pass to create or update registrations. It contains array of json of the fields matching MICEtribe persona fields settings. - barcode: this is optional field that is used to replace MICEtribe QR code with barcode sent via api - parent_barcode: this is optional fields that is used to create this registration as member of another registration. (it's used for group registration) - enable_comms: this is optional filed that is used to enable sending communications via system, currently email and SMS communication are supported. Default value for it is false. to turn it on, pass boolean true value to the field. Fields validations: - phone_number field must have at least 5 charachters and be in international format so it should start with 00 or +. Successful examples of phone number are e.g 0097466666666 or +97466666666 or 97466666666 - email field must have valid email format and valid DNS - country field accepts ISO 2-letter code, ISO 3-letter code - website field shuld be valid URL format - upload field must have valie url for uploaded file - date field must be in this format yyyy-mm-dd and it can has time e.g yyyy-mm-dd hh:MM:ss - numberic field must have numbers only ### Get Registrations - [GET /registration](https://developer.micetribe.com/apis/registration/paths/~1registration/get.md): ## Registration - List Registrations Retrieves a paginated list of registration records. Useful for admin dashboards and reporting. ### Method & URL - GET {{base_url}}/registration ### Query Parameters - page (number, optional) — Page number to fetch. Defaults to 1. - per_page (number, optional) — Items per page. Common values: 5, 20. Defaults to 5. - persona (string, optional) — Filter by user persona. Example: visitor. - barcode (string, optional) — Filter by barcode. Example: 0IG6XSAD. ### Headers - Accept: application/json - Accept-Encoding: application/json ### Authentication - Uses environment variable {{token}} if your API requires Bearer or API key auth. Ensure the active environment (e.g., Sandbox or Live) has this value set. ### Variables - {{base_url}} — Base host for the API, provided by the active environment. ### Expected Responses - 200 OK — Returns an array of registration objects with pagination metadata. - 400/422 — Validation errors for bad parameters. - 401 — Missing/invalid credentials if the endpoint is protected. ### Usage Notes - Combine persona and barcode to narrow results. - Use smaller per_page during development to limit payload size. ### Examples - GET {{base_url}}registration?page=1&per_page=5 — First page with 5 items. - GET {{base_url}}registration?page=3&per_page=20&persona=visitor — Third page, filtered by persona. - GET {{base_url}}registration?barcode=34DD490 — Filter by person barcode ### Delete Registration - [DELETE /registration/{registratoin_id}](https://developer.micetribe.com/apis/registration/paths/~1registration~1%7Bregistratoin_id%7D/delete.md): Delete api can delete any registration in the allowed event. ## Event ### Get Event - [GET /event](https://developer.micetribe.com/apis/event/paths/~1event/get.md): 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.