# Get a list of usage overrides

Endpoint: GET /usage-rate-overrides
Version: 1.15
Security: bearerAuth

## Query parameters:

  - `page` (integer, required)
    Page of results to show
    Example: 1

  - `pageSize` (integer, required)
    Results to return per page
    Example: 100

  - `sort` (string)
    Comma-delimited list of the fields to sort by - defaults to ascending order, suffix :desc to change
    Example: "id,name | name:desc"

  - `fields` (string)
    Comma-delimited list of the field(s) to return if only a subset is required
    Example: "id,name"

  - `assignmentLevel` (string)
    Filter by assignment level - CUSTOMER, SITE or INVENTORY
    Example: "xyz | in:x,y | like:xyz"

  - `customerId` (string)
    Filter by customer
    Example: "0"

  - `siteId` (string)
    Filter by site
    Example: "0"

  - `usageProductInventoryId` (string)
    Filter by usage product inventory
    Example: "0"

  - `usageProductId` (string)
    Filter by usage product
    Example: "0"

  - `startDate` (string)
    Filter by start date
    Example: "yyyy-MM-dd | lt:yyyy-MM-dd | gt:yyyy-MM-dd | gtn:yyyy-MM-dd"

  - `endDate` (string)
    Filter by end date
    Example: "yyyy-MM-dd | lt:yyyy-MM-dd | gt:yyyy-MM-dd | gtn:yyyy-MM-dd"

## Response 200 fields (application/json):

  - `id` (integer)
    Usage rate override identifier
    Example: 1

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

  - `usageProductId` (integer, required)
    Usage product identifier
    Example: 1

  - `supplierId` (integer)
    Supplier identifier
    Example: 1

  - `chargeGroupId` (integer, required)
    Charge group identifier
    Example: 1

  - `variableChargeUnitSize` (integer, required)
    Variable charge unit size
    Example: 60

  - `quantityRoundingIncrement` (number, required)
    Quantity rounding increment
    Example: 1

  - `startDate` (string, required)
    Start date

  - `appliesToISDNOnly` (boolean)
    Applies to ISDN calls only?

  - `endDate` (string)
    End date

  - `peakValue` (number)
    Peak value

  - `offPeakValue` (number)
    Off peak value

  - `weekendValue` (number)
    Weekend value

  - `peakMinimumCharge` (number, required)
    Peak minimum charge

  - `offPeakMinimumCharge` (number, required)
    Off peak minimum charge

  - `weekendMinimumCharge` (number, required)
    Weekend minimum charge

  - `peakInitialCharge` (number, required)
    Peak initial charge

  - `offPeakInitialCharge` (number, required)
    Off peak initial charge

  - `weekendInitialCharge` (number, required)
    Weekend initial charge

  - `peakInitialChargePeriod` (integer, required)
    Peak initial charge period

  - `offPeakInitialChargePeriod` (integer, required)
    Off peak initial charge period

  - `weekendInitialChargePeriod` (integer, required)
    Weekend initial charge period


## Response 400 fields

## Response 401 fields

## Response 404 fields

## Response 412 fields

## Response 500 fields

## Response 501 fields