---
title: "Get all routing rules"
method: POST
path: "/api/connector/v1/routingRules/getAll"
tags: ["Routing rules"]
deprecated: true
---

# Get all routing rules

`POST /api/connector/v1/routingRules/getAll`

> **Deprecated.**

Use [Get all billing automations](https://mews-systems.gitbook.io/connector-api/operations/billingautomations#get-all-billing-automations).

## Request body

- RoutingRuleFilterParameters
  - `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.
  - `CompanyIds` string[], nullable — Unique identifier of the `Company`.
  - `RoutingRuleIds` string[], nullable — Unique identifier of the routing rules.
  - `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

- RoutingRuleResult
  - `RoutingRules` RoutingRule[], required — Collection of routing rules.
    - `Id` string, uuid, required — Unique identifier of the routing rule.
    - `EnterpriseId` string, uuid, required — Unique identifier of the Enterprise.
    - `CompanyId` string, uuid, required — Unique identifier of the Company routing rule is assigned to.
    - `CompanyRelation` 'PartnerCompany' | 'TravelAgency', required — Relation of the company to the routing rule.
    - `Applicability` 'Always' | 'PrepaidOnly', required — Determines if routing rule applies to all future reservations with this company or travel agency, or only future reservations that are prepaid.
    - `RouteType` 'AllStayItems' | 'SelectedStayItems', required — Determines to which stay items the routing rule applies.
    - `ServiceId` string, uuid, required — Unique identifier of the Service routing rule is assigned to.
    - `SelectedStayItems` RoutingRuleStayItems
      - `Nights` boolean — Whether the routing rule applies to nights.
      - `CityTax` boolean — Whether the routing rule applies to city tax.
      - `ProductCategoryIds` string[], nullable — Product categories to which the routing rule applies to.
    - `CreatedUtc` string, date-time, required — Creation date and time of the routing rule in UTC timezone in ISO 8601 format.
    - `UpdatedUtc` string, date-time, required — Last update date and time of the routing rule 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/revisions/f37f136ed35a/schema)