Assigns a rate (tariff) to an account-meter relationship
Use this endpoint to assign a tariff/rate schedule to an account-meter relationship. The rate defines how usage
and demand charges are calculated for bills on this meter. The rate’s begin date must fall within the account-meter’s
date range. Multiple rates can be assigned over time to track tariff changes.
To replace all rate assignments at once, use PUT /accountmeter/{accountMeterId}/rate.
Request Headers
| Header | Value | Required | Description |
|---|---|---|---|
| ECI-ApiKey | string | Yes | Your API key. See Authentication. |
| Content-Type | application/json | Yes | All requests must specify JSON content type, including the request body. |
Path Parameters
| Name | Description | Type | Required |
|---|---|---|---|
| accountMeterId | The unique numeric identifier of the account-meter relationship to assign the rate to | integer (int32) | Required |
Request Body
AccountRateRequest
| Property | Description | Type |
|---|---|---|
| rateId | The identifier for the rate to assign to the accountMeter Required Required | integer (int32) |
| startDate | The start date for the accountRate Required Required | string (date-time) |
Example Request Body
{ "rateId": 1, "startDate": "2026-06-29"
}Responses
200
OK
The request succeeded and the response body contains the requested data.
Response Body Parameters
AccountMeterRateResponse
| Property | Description | Type |
|---|---|---|
| endDate | The end date for the rate on the account meter Required (defined) | string (date-time) |
| name | The rate name Required (defined) | string |
| note | The rate’s note Required (defined) | string |
| rateCode | The rate code Required (defined) | string |
| rateId | The account meter tariff identifier Required (defined) | integer (int32) |
| startDate | The start date for the rate on the account meter Required (defined) | string (date-time) |
Example Response
{ "endDate": "2026-06-29", "name": "string", "note": "string", "rateCode": "string", "rateId": 1, "startDate": "2026-06-29"
}
404
Not Found
The requested resource was not found. Verify the ID or path is correct.