Process reservation
POST /api/connector/v1/reservations/process
Marks a reservation as Processed (= checked out). Succeeds only if all processing conditions are met (the reservation has the Started state, balance of all reservation members is zero etc). Note this operation supports Portfolio Access Tokens.
Conditions
- Reservation has already been checked in.
- Reservation isn’t alredy in
Processedstate. - Reservation can’t be checked out sooner than last day of planned stay.
- The companion profiles of reservation are complete (details can be found in error message).
- If
AllowOpenBalanceset tofalse, all bills have to be closable (items on bills are either paid by current customer, or set to be paid by other customer). WithCloseBillsoption set totruethey can be automatically closed, when set tofalsethey must be closed manually. - If
AllowOpenBalanceset totrue,Notesmust be filled in.
Request Body
Section titled “Request Body ”object
Token identifying the client application.
Access token of the client application.
Name and version of the client application.
Unique identifier of the enterprise. Required when using Portfolio Access Tokens, ignored otherwise.
Unique identifier of the reservation to process.
Whether closable bills of the reservation members should be automatically closed.
Whether non-zero consumed balance of all reservation members is allowed.
Required if AllowOpenBalance set to true. Used to provide reason for closing with unbalanced bill.
Example
{ "ClientToken": "E0D439EE522F44368DC78E1BFB03710C-D24FB11DBE31D4621C4817E028D9E1D", "AccessToken": "C66EF7B239D24632943D115EDE9CB810-EA00F8FD8294692C940F6B5A8F9453D", "Client": "Sample Client 1.0.0", "EnterpriseId": "3fa85f64-5717-4562-b3fc-2c963f66afa6", "ReservationId": "e6ea708c-2a2a-412f-a152-b6c76ffad49b", "CloseBills": false, "AllowOpenBalance": false, "Notes": null}Responses
Section titled “ Responses ”OK
object
Server has successfully fulfilled the request and there is no additional information to send back.
object
Error caused by the client app, e.g. in case of malformed request or invalid identifier of a resource. In most cases, such an error signifies a bug in the client app (consumer of the API).
object
Error caused by usage of invalid ClientToken, AccessToken, or you may not have the necessary permission to use the endpoint.
object
Server error that should be reported to the end user of the client app. Happens for example when the server-side validation fails or when a business-logic check is violated.
object
Error caused by heavy request that takes too long to process (typically tens of seconds). To get around this, request data in smaller batches. For more information, see Request timeouts
object
Error caused by too many requests sent in a given amount of time. Response contains Retry-After header indicating how long the user agent should wait before making a follow-up request. For more information, see Request limits.
object
Unexpected error on the Mews side. This may be due to a software fault. If such a situation occurs, the error will be logged and the development team notified, however you can raise an issue through GitHub on our documentation repository.