Pay attention! Before you can continue you will need an API key. You can request this via the chat.
With a request header
Set the X-Authorization request header as follows for each request:
With a query parameter
Add the key parameter to your url as follows:
The API can only be used with the JSON format.
"message": "Request validation failed",
"locale": "This field is incorrect"
Ondersteunde velden in MICE Operations
Start date and time of the event.
End date and time of the event.
The name of the event. We recommend that you always enter an event name. Possibly composed of several fields from the form. See example.
The group name.
A specific name for the notepad.
The number of persons. This must be a number.
The client's language preference. (ISO code, e.g. nl_NL or en_US)
A reference number or code
Company name of the client.
Street name and house number of the client.
Additional address line for the client's address.
Postal code of the client.
Place name of the client.
Country of the client.
First name of the client.
Surname of the client.
Telephone number of the client.
E-mail address of the client.
Internal notes at booking.
Additional comments from the client.
In MICE Operations you can look up the ID number of a specific location under management. You can pass on this number to link the event directly to the location or room.
In MICE Operations you can look up the ID number of an event type under management (e.g. Meeting, Workshop, etc). You can give this number to link the event directly to a certain type of event.
In the source field you can enter a reference to the form. In this way you can later retrieve in reports how different forms and application modules perform.
Creating an event
name: "Test event",
group_name: "MICE Operations",
source: "Webhook documentation",
question: "Any remarks?",
answer: "I would like to have sweet potatoes"
201 – Event was successfully created
401 – Authorization failed (incorrect or disabled key)
422 – Data validation failed