Schema for creating is the the same as for Create time slot reservation .
Auth:PATCH {baseUrl}/queues/{queueId}/reservations/{positionId}
The parameters and structure are identical to those used in the creation of a time slot reservation, ensuring consistency across API interactions.
Authentication
ApiKey header (
...
organizational key) is required.
Request:
| Code Block |
|---|
curl --location --request PATCH 'https://ombori-queue-qa.azure-api.net/api/organizations/{organizationName{baseUrl}/queues/{queueId}/reservations/{positionId}' \ --header 'Content-Type: application/json' \ --header 'ApiKey: XYZ' \ --data-raw '{ "locale": "en", "notification": { "type": "phoneNumber", "settings": { "to": "+48000" } }, "customerInfo": ["Firstname Lastname"], "numberOfPeople": 2, "booking": { "start": "2020-11-30T14:40:00.000Z", "end": "2020-11-30T14:45:00.000Z", "virtualAppointment": { "isEnabled": true } }, "customData": { "internalIdOrAnyOtherField": "foo", } }' |
...