--- title: "Get all services" method: POST path: "/api/connector/v1/services/getAll" tags: ["Services"] --- # Get all services `POST /api/connector/v1/services/getAll` Returns all services offered by the enterprise. Note this operation uses [Pagination](https://mews-systems.gitbook.io/connector-api/guidelines/pagination/) and supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property). ## Request body - ServiceFilterParameters - `ClientToken` string, required — Token identifying the client application. - `AccessToken` string, required — Access token of the client application. - `Client` string, required — Name and version of the client application. - `Limitation` Limitation, required — Limitation on the quantity of data returned. - `Count` integer, required - `Cursor` string, uuid, nullable - `EnterpriseIds` string[], nullable — Unique identifiers of the Enterprises. If not specified, the operation returns data for all enterprises within scope of the Access Token. - `ServiceIds` string[], nullable — Unique identifiers of [Services](https://mews-systems.gitbook.io/connector-api/operations/services/#service). - `ServiceType` 'Bookable' | 'Additional' — Bookable Additional - `UpdatedUtc` TimeFilterInterval — When a time interval is used for **filtering** (for example in parameters such as `CreatedUtc.StartUtc` / `CreatedUtc.EndUtc`), the following rules apply: - **Start equals End (equality mode)** If `StartUtc` and `EndUtc` are exactly the same timestamp, the filter is treated as an equality check for that precise moment in time: ``` CreatedUtc == StartUtc ``` This does not represent an interval; only records with `CreatedUtc` equal to that exact instant are returned. - **Start differs from End (interval mode)** If `StartUtc` and `EndUtc` are different, the filter is evaluated as a half-open interval: ``` StartUtc <= CreatedUtc < EndUtc ``` In other words, the start is inclusive and the end is exclusive. Make sure your integration takes inclusive Start / exclusive End behavior of time intervals into account so that no records at the boundaries are omitted. - `StartUtc` string, date-time, nullable - `EndUtc` string, date-time, nullable ## Response `200` OK - ServiceResult - `Services` Service[], required — Services offered by the enterprise. - `Id` string, uuid, required — Unique identifier of the service. - `EnterpriseId` string, uuid, required — Unique identifier of the [Enterprise](https://mews-systems.gitbook.io/connector-api/operations/enterprises/#enterprise). - `IsActive` boolean, required — Whether the service is still active. - `Name` string, required — Name of the service. - `Names` object, required — All translations of the name. - `StartTime` string, nullable - `EndTime` string, nullable - `Options` ServiceOptions, required — Options of the service. - `BillAsPackage` boolean, required — Products should be displayed as a single package instead of individual items. - `Promotions` Promotions - `BeforeCheckIn` boolean, required — Whether it can be promoted before check-in. - `AfterCheckIn` boolean, required — Whether it can be promoted after check-in. - `DuringStay` boolean, required — Whether it can be promoted during stay. - `BeforeCheckOut` boolean, required — Whether it can be promoted before check-out. - `AfterCheckOut` boolean, required — Whether it can be promoted after check-out. - `DuringCheckOut` boolean, required — Whether it can be promoted during check-out. - `Type` string, nullable - `Ordering` integer, required — Order value for presentation purposes. - `Data` object, required — Additional information about the specific service. - `Discriminator` 'Bookable' | 'Additional' - `Value` union - BookableServiceData - `StartOffset` string, required — Offset from the start of the [time unit](https://mews-systems.gitbook.io/connector-api/concepts/time-units/) which defines the default start of the service; expressed in ISO 8601 duration format. - `EndOffset` string, required — Offset from the end of the [time unit](https://mews-systems.gitbook.io/connector-api/concepts/time-units/) which defines the default end of the service; expressed in ISO 8601 duration format. - `OccupancyStartOffset` string, required — Offset from the start of the [time unit](https://mews-systems.gitbook.io/connector-api/concepts/time-units/) which defines the occupancy start of the service; expressed in ISO 8601 duration format. 'Occupancy start' is used for availability and reporting purposes, it implies the time at which the booked resource is considered occupied. - `OccupancyEndOffset` string, required — Offset from the end of the [time unit](https://mews-systems.gitbook.io/connector-api/concepts/time-units/) which defines the occupancy end of the service; expressed in ISO 8601 duration format. 'Occupancy end' is used for availability and reporting purposes, it implies the time at which the booked resource is no longer considered occupied. - `TimeUnit` 'Day' | 'Month' | 'Hour', required — Day Month Hour - `TimeUnitPeriod` 'Day' | 'Month' | 'Hour', required — Day Month Hour - AdditionalServiceData - `Promotions` Promotions, required - `BeforeCheckIn` boolean, required — Whether it can be promoted before check-in. - `AfterCheckIn` boolean, required — Whether it can be promoted after check-in. - `DuringStay` boolean, required — Whether it can be promoted during stay. - `BeforeCheckOut` boolean, required — Whether it can be promoted before check-out. - `AfterCheckOut` boolean, required — Whether it can be promoted after check-out. - `DuringCheckOut` boolean, required — Whether it can be promoted during check-out. - `ExternalIdentifier` string, nullable — Identifier of the service from external system. - `CreatedUtc` string, date-time, required — Creation date and time of the service in UTC timezone in ISO 8601 format. - `UpdatedUtc` string, date-time, required — Last update date and time of the service in UTC timezone in ISO 8601 format. - `Cursor` string, uuid, nullable — 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. ## Other responses - `204` — Server has successfully fulfilled the request and there is no additional information to send back. - `400` — 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). - `401` — Error caused by usage of invalid ClientToken, AccessToken, or you may not have the necessary permission to use the endpoint. - `403` — 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. - `408` — 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](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-timeouts) - `429` — 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](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-limits). - `500` — 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](https://github.com/MewsSystems/gitbook-connector-api). --- [API](https://skmtc.net/mews/apis/connector-api.md) · [All operations](https://skmtc.net/mews/apis/connector-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mews/connector-api/versions/81933a8ff730/schema)