# Update an inclusive usage plan assignment

Endpoint: PATCH /inclusive-usage-plan-assignments/{assignmentLevel}/{inclusive_usage_plan_assignment_id}
Version: 1.15
Security: bearerAuth

## Path parameters:

  - `assignmentLevel` (string, required)
    Assignment level to be updated - CUSTOMER, SITE or INVENTORY
    Enum: "CUSTOMER", "SITE", "INVENTORY"

  - `inclusive_usage_plan_assignment_id` (integer, required)
    Inclusive usage plan assignment identifier
    Example: 1

## Request fields (application/json-patch+json):

  - `op` (string, required)
    The JSON Patch operation to be performed
    Enum: "add", "remove", "replace", "move", "copy", "test"

  - `path` (string, required)
    A JSON-Pointer

  - `value` (object)
    The value to be used within the operations

  - `from` (string)
    A string containing a JSON Pointer value

## Response 200 fields (application/json):

  - `id` (integer)
    Inclusive usage plan assignment identifier
    Example: 1

  - `assignmentLevel` (string, required)
    Inclusive usage plans can be assigned at customer, site or product inventory levels - use the appropriate level to determine which fields are required.
    Example: "CUSTOMER, SITE or INVENTORY"

  - `inclusiveUsagePlanId` (integer, required)
    Inclusive usage plan identifier
    Example: 1

  - `startDate` (string, required)
    Start date

  - `endDate` (string)
    End date


## Response 400 fields

## Response 401 fields

## Response 403 fields

## Response 404 fields