--- title: "Get all cancellation policies (ver 2026-07-31)" method: POST path: "/api/connector/v1/cancellationPolicies/getAll/2026-07-31" tags: ["Cancellation policies"] --- # Get all cancellation policies (ver 2026-07-31) `POST /api/connector/v1/cancellationPolicies/getAll/2026-07-31` ## Request - Base URL: `https://api.mews.com` - URL: `https://api.mews.com/api/connector/v1/cancellationPolicies/getAll/2026-07-31` - Auth: none declared - TypeScript: (a function with typed inputs; its response is checked against the schema) Returns the current versions of cancellation policies within the enterprise scope in the same shape as the `add`, `update` operations, including policies that are not currently assigned to any rate or reservation. Historical versions produced by fee-affecting updates are not returned. Optionally filtered by `CancellationPolicyIds`, `UpdatedUtc`, and `ActivityStates`; when no filter is provided all current cancellation policies within the enterprise scope are returned. 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 - CancellationPolicyFilterParametersV20260731 - `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. - `CancellationPolicyIds` string[], nullable: Unique identifiers of the requested cancellation policies. If not specified, all current cancellation policy versions within the enterprise scope are returned. - `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 - `ActivityStates` ActivityStates[], nullable: Whether to return only active, only deleted, or both types of record. If not specified, only active records will be returned. ## Response `200` OK - CancellationPolicyResultV20260731 - `CancellationPolicies` CancellationPolicyModificationData[], required: The requested cancellation policies. - `Id` string, uuid, required: Unique identifier of the cancellation policy. - `EnterpriseId` string, uuid, required: Unique identifier of the enterprise the cancellation policy belongs to. - `CreatedUtc` string, date-time, required: Creation date and time of the cancellation policy in UTC timezone in ISO 8601 format. - `UpdatedUtc` string, date-time, required: Last update date and time of the cancellation policy in UTC timezone in ISO 8601 format. - `IsActive` boolean, required: Whether the cancellation policy is still active. - `Applicability` 'Creation' | 'Start' | 'StartDate', required: Applicability mode of the cancellation policy. Creation Start StartDate - `FeeExtents` CancellationFeeExtentEnum[], required: Extent for the cancellation fee, i.e. what should be in scope for the automatic payment. - `ApplicabilityOffset` string, required: Offset from which the fee is applied in ISO 8601 duration format. - `FeeMaximumTimeUnits` integer, nullable: Maximum number of time units the cancellation fee is applicable to. - `AbsoluteFee` CurrencyValue, required: Absolute value of the fee. - `Currency` string, currency, required: ISO-4217 code of the `Currency`. - `Value` number, double, required: Amount in the currency. - `RelativeFee` number, double, required: Relative value of the fee, as a percentage of the reservation price. - `Name` string, nullable: Name of the cancellation policy. - `ExternalIdentifier` string, nullable: Identifier of the cancellation policy from an external system, unique within the enterprise, that can be used to reference the policy from your own system. - `IsPortfolioManaged` boolean, required: Whether the cancellation policy is managed by the portfolio. Policies managed by the portfolio cannot be updated or deleted through this resource. - `Cursor` string, string, nullable: Opaque pagination cursor which can be used in `Limitation` to fetch further cancellation policies. ## 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). ## Changes - **2026-08-12** `66301d8e85af`: 1 info - endpoint added [Operation history](https://skmtc.dev/mews/apis/connector-api/changes/api/connector/v1/cancellationPolicies/getAll/2026-07-31/post.md) --- [API](https://skmtc.dev/mews/apis/connector-api.md) - [All operations](https://skmtc.dev/mews/apis/connector-api/llms.txt) - [OpenAPI document](https://skmtc.dev/mews/apis/connector-api/revisions/cabf1b2da1d0?raw)