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

# Update routing rules

`POST /api/connector/v1/routingRules/update`

> **Deprecated.**

Use [Update billing automations](https://mews-systems.gitbook.io/connector-api/operations/billingautomations#update-billing-automations) and [Update billing automations assignments](https://mews-systems.gitbook.io/connector-api/operations/billingautomations#update-billing-automations-assignments).

## Request body

- MultipleRoutingRuleUpdateParameters
  - `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.
  - `RoutingRuleUpdates` RoutingRuleUpdateParameters[], required — Collection of Routing rules to be updated.
    - `RoutingRuleId` string, uuid, required — Unique identifier of the routing rule.
    - `CompanyId` GuidUpdateValue
      - `Value` string, uuid — Value which is to be updated.
    - `ServiceId` GuidUpdateValue
      - `Value` string, uuid — Value which is to be updated.
    - `CompanyRelation` StringUpdateValue
      - `Value` string, nullable — Value which is to be updated.
    - `Applicability` StringUpdateValue
      - `Value` string, nullable — Value which is to be updated.
    - `RouteType` StringUpdateValue
      - `Value` string, nullable — Value which is to be updated.
    - `AssignmentTargetType` StringUpdateValue
      - `Value` string, nullable — Value which is to be updated.
    - `SelectedStayItems` RoutingRuleStayItemsUpdateParameters
      - `Nights` BooleanUpdateValue
        - `Value` boolean — Value which is to be updated.
      - `CityTax` BooleanUpdateValue
        - `Value` boolean — Value which is to be updated.
      - `ProductCategoryIds` GuidIEnumerableUpdateValue
        - `Value` string[], nullable — Value which is to be updated.

## Response `200`

OK

- RoutingRuleUpdateResult
  - `RoutingRules` RoutingRule[], required — Updated 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.

## 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)