# Create peel off report

Create a peel off report for a given time range and set of monitors.

Endpoint: POST /peel-off-reports
Version: 0.0.1
Security: o_auth

## Request fields (application/json):

  - `endDate` (string)
    It is the upper bound of the date range for which to return data. The endDate is non-inclusive; i.e, the returned data will be for dates from startDate to endDate-1. If provided will take precedence over endAt.

  - `isOpen` (boolean)
    Flag to filter output within site opening hour window

  - `peelOffMonitorIds` (array)
    List of peel off monitor ids in the report. At least one id is required.

  - `startDate` (string)
    It is the lower bound of the date range for which to return data. The startDate is inclusive; i.e, the returned data will be for dates from startDate to endDate-1.

  - `timeGrain` (string)
    The time window in the requested range to for data aggregation.
    Enum: "1s", "1m", "5m", "15m", "30m", "1h", "6h", "24h"

## Response 200 fields (application/json):

  - `base` (integer,null)

  - `id` (string)

  - `name` (string)

  - `peelOff` (integer,null)

  - `rate` (number,null)

  - `time` (string)

## Response 400 fields (application/json):

  - `code` (integer)

  - `message` (string)

## Response 401 fields (application/json):

  - `code` (integer)

  - `message` (string)

## Response 403 fields (application/json):

  - `code` (integer)

  - `message` (string)

## Response 413 fields (application/json):

  - `code` (integer)

  - `message` (string)

## Response 422 fields (application/json):

  - `code` (integer)

  - `message` (string)

## Response 500 fields (application/json):

  - `code` (integer)

  - `message` (string)