# Create a new inclusive usage plan assignment

Endpoint: POST /inclusive-usage-plan-assignments
Version: 1.15
Security: bearerAuth

## Request fields (application/json):

  - `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 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 201 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 404 fields

## Response 412 fields

## Response 500 fields

## Response 501 fields