Get all service overbooking limits
POST /api/connector/v1/serviceOverbookingLimits/getAll
Returns all service overbooking limits. Note this operation uses Pagination and supports Portfolio Access Tokens.
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.
Limitation on the quantity of data returned and optional Cursor for the starting point of data.
object
Unique identifiers of the Enterprises. If not specified, the operation returns data for all enterprises within scope of the Access Token.
Unique identifiers of Service associated with the service overbooking limits.
Unique identifiers of the service overbooking limits.
Interval in which the service overbooking limit is active.
object
Interval in which the service overbooking limits were updated.
object
Whether to return only active, only deleted, or both types of record. If not specified, only active records will be returned.
Example
{ "ClientToken": "E0D439EE522F44368DC78E1BFB03710C-D24FB11DBE31D4621C4817E028D9E1D", "AccessToken": "C66EF7B239D24632943D115EDE9CB810-EA00F8FD8294692C940F6B5A8F9453D", "Client": "Sample Client 1.0.0", "ServiceIds": [ "bd26d8db-86da-4f96-9efc-e5a4654a4a94", "8c1bd738-a505-4b29-aa71-9ecc2982b843" ], "ServiceOverbookingLimitIds": [ "e654f217-d1b5-46be-a820-e93ba568dfac" ], "CollidingUtc": { "StartUtc": "2024-11-01T00:00:00Z", "EndUtc": "2024-11-30T00:00:00Z" }, "UpdatedUtc": { "StartUtc": "2024-11-01T00:00:00Z", "EndUtc": "2024-11-30T00:00:00Z" }, "ActivityStates": [ "Active" ], "EnterpriseIds": [ "3fa85f64-5717-4562-b3fc-2c963f66afa6", "4d0201db-36f5-428b-8d11-4f0a65e960cc" ], "Limitation": { "Count": 100, "Cursor": "e7f26210-10e7-462e-9da8-ae8300be8ab7" }}Responses
Section titled “ Responses ”OK
object
Service overbooking limits of the default service.
object
Unique identifier of the service overbooking limit.
Unique identifier of the Service.
Start of the time interval, expressed as the timestamp for the start of the first time unit, in UTC timezone ISO 8601 format.
End of the time interval, expressed as the timestamp for the start of the last time unit, in UTC timezone ISO 8601 format.
Number of overbookings allowed for the Service.
Timestamp in UTC timezone ISO 8601 format when the service overbooking was created.
Timestamp in UTC timezone ISO 8601 format when the service overbooking was updated.
Whether the service overbooking limit is still active.
Unique identifier of the item one newer in time order than the items to be returned. If Cursor is not specified, i.e. null, then the latest or most recent items will be returned.
Example
{ "ServiceOverbookingLimits": [ { "Id": "e654f217-d1b5-46be-a820-e93ba568dfac", "ServiceId": "3fa85f64-5717-4562-b3fc-2c963f66afa6", "FirstTimeUnitStartUtc": "2024-11-01T00:00:00Z", "LastTimeUnitStartUtc": "2024-11-30T00:00:00Z", "Limit": 10, "CreatedUtc": "2024-01-31T10:48:06Z", "UpdatedUtc": "2024-01-31T10:58:06Z", "IsActive": true } ], "Cursor": "e654f217-d1b5-46be-a820-e93ba568dfac"}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.