# Save Mid-Invoice Cycle Charge Estimation

Save Mid-Invoice Cycle Charge Estimation

Endpoint: POST /rest/2.0/INVOICE_ESTIMATE_CONFIG
Version: 1.0
Security: JWT

## Header parameters:

  - `sessionId` (string, required)

## Request fields (application/json; charset=utf-8):

  - `brmObjects` (object)

  - `brmObjects.EstimateHour` (string)
    Hour of the Day to Estimate Charges on (in GMT): Mid-Invoice Cycle Charge Estimation Job will run daily at the hour specified

  - `brmObjects.RuleCriteria` (string)
    Invoice Admission Criteria

  - `brmObjects.Rule` (string)
    Formula

  - `brmObjects.FilterLogic` (string)
    Criteria Join Logic: Use this to define the logical grouping of your filter criteria. The ordered list of Filters defined above can be segregated to more narrowly define the filter as a whole. So lets say you have three filters. Use this field to define more meaning across the three. For example: (1 AND 2 ) OR 3. Use parentheses as well as AND and OR operators to define the filter logic.

  - `brmObjects.Enabled` (integer)
    Enable Scheduled Mid-Invoice Cycle Charge Estimation

  - `brmObjects.EnableAdHoc` (integer)
    Allow mid-invoice cycle estimation via UI and API: When checked enables generation of estimate invoices by either the UI or API channels

  - `brmObjects.Id` (string, required)
    Id: INVOICE_ESTIMATE_CONFIG_ID

## Response 200 fields (application/json):

  - `retrieveResponse` (object)

  - `retrieveResponse.EstimateHour` (string)
    Hour of the Day to Estimate Charges on (in GMT): Mid-Invoice Cycle Charge Estimation Job will run daily at the hour specified

  - `retrieveResponse.RuleCriteria` (string)
    Invoice Admission Criteria

  - `retrieveResponse.Rule` (string)
    Formula

  - `retrieveResponse.FilterLogic` (string)
    Criteria Join Logic: Use this to define the logical grouping of your filter criteria. The ordered list of Filters defined above can be segregated to more narrowly define the filter as a whole. So lets say you have three filters. Use this field to define more meaning across the three. For example: (1 AND 2 ) OR 3. Use parentheses as well as AND and OR operators to define the filter logic.

  - `retrieveResponse.Enabled` (integer)
    Enable Scheduled Mid-Invoice Cycle Charge Estimation

  - `retrieveResponse.EnableAdHoc` (integer)
    Allow mid-invoice cycle estimation via UI and API: When checked enables generation of estimate invoices by either the UI or API channels

  - `retrieveResponse.Id` (string)
    Id: INVOICE_ESTIMATE_CONFIG_ID

## Response 400 fields (application/json):

  - `error` (string)
    Bad request

  - `message` (string)
    Bad request

## Response 401 fields (application/json):

  - `error` (string)
    Unauthorized

  - `message` (string)
    Unauthorized

## Response 404 fields (application/json):

  - `error` (string)
    Not found

  - `message` (string)
    Not found

## Response 429 fields (application/json):

  - `error` (string)
    Too many requests

  - `message` (string)
    Too many requests

## Response 500 fields (application/json):

  - `error` (string)
    Internal error

  - `message` (string)
    Internal error