Use the prices/connector_prices
endpoint to retrieve a collection of pricing_ids
with their respective location_id
, evse_uid
, and connector_id
.
Request
See prices/connector-prices to know more about the parameters that are used with the prices/connector_prices
endpoint.
Response
The following is a sample response for the prices/connector_prices
endpoint:
{
data: [
{ pricing_ids: [
...
]
}
],
}
Caution
Eco-Movement always upholds the API contract, but we may send new attributes in our JSON response when:
- we add an OCPI mandatory attribute to the JSON response to be OCPI compliant
- we improve your licensing module with new features
Hence, we strongly recommend that you handle or ignore unknown JSON fields.
Response Definitions
The following are the attributes for the prices/connector_prices
endpoint:
Attribute | Description |
---|---|
data.location_id | The unique id for a location. It is created by Eco-Movement, and it is stable. This attribute may change when two or more locations are merged, which results in one location only. |
data.evse_uid | The unique ID of an EVSE in the system of the CPO. It is created by the CPO and is not unique within Eco-Movement's database. Note: Use this attribute for PATCH requests as an evse's id. |
data.connector_id | The identifier of the connector within the EVSE created by the CPO. Two connectors may have the same id as long as they do not belong to the same EVSE object. |
data.pricing_ids | The unique ids for the prices that are set to the connector. Note: They are created by Eco-Movement and is refreshed whenever a price or product associated with that particular id is updated. |
Note
Use the "Try It!" button in prices/connector-prices to view an actual response from our API.