---
title: "Update customer mappings for a rule"
method: PUT
path: "/msp/dataProtection/v1/rules/{rule_id}/customers"
tags: ["Data Protection"]
---

# Update customer mappings for a rule

`PUT /msp/dataProtection/v1/rules/{rule_id}/customers`

Replaces the customers mapped to a data protection rule.

## Path parameters

- `rule_id` string, required

## Headers

- `Authorization` string, required

## Request body

- DataProtectionUpdateCustomersRequest — UpdateCustomersRequest represents update customers for rule API request
  - `customerGlobalIDs` string[], required — List of customer global IDs to map to this rule (complete replacement)

## Response `200`

Ok - Customers updated successfully

## Other responses

- `400` — Bad Request - Invalid customer IDs, missing license, or restricted customers
- `401` — The request did not include a valid Access Token. Kindly provide a valid Access Token to process the request.
- `403` — Forbidden - Insufficient permissions
- `404` — Not Found - Rule does not exist or does not belong to MSP
- `500` — The request was not processed due to an internal error. Kindly try again later. If the error persists, contact Druva Support.

---

[API](https://skmtc.net/druva/apis/authentication.md) · [All operations](https://skmtc.net/druva/apis/authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/druva/authentication/revisions/2af2bf148b25/schema)