# Enectiva REST API - Librarian

## Docs
- [Introduction](https://apidocs.enectiva.cz/introduction-1363538m0.md): 
- Deltas [Introduction to Deltas](https://apidocs.enectiva.cz/introduction-to-deltas-1524333m0.md): 

## API Docs
- Access tokens [Create a new access token](https://apidocs.enectiva.cz/create-a-new-access-token-19188091e0.md): This action allows you to use the long-lived login token and obtain a short-lived access token which you can then use to access other resources. The access token is a [JWT](https://en.wikipedia.org/wiki/JSON_Web_Token) that you can inspect, verify the permissions and validity.
- Data points from Enectiva [List data points of a data series](https://apidocs.enectiva.cz/list-data-points-of-a-data-series-19188092e0.md): This action allows to list data points of a single data series. Only valid and fully processed data points are included. The values can be [sorted](apidog://link/pages/1363538#sort-options), the default order is chronological.
- Deltas [List monthly deltas of an entity](https://apidocs.enectiva.cz/list-monthly-deltas-of-an-entity-19188093e0.md): This action allows to list monthly deltas of a single entity. Entity is any
- Deltas [List monthly deltas of a meter](https://apidocs.enectiva.cz/list-monthly-deltas-of-a-meter-19188094e0.md): This action allows to list monthly deltas of a single meter. Values are in the
- Deltas [List monthly deltas of a virtual meter](https://apidocs.enectiva.cz/list-monthly-deltas-of-a-virtual-meter-19188095e0.md): This action allows to list monthly deltas of a single virtual meter. Values are in the
- Data points to Enectiva [Latest data point](https://apidocs.enectiva.cz/latest-data-point-19188098e0.md): Latest data point endpoint is an equivalent to latest reading endpoint with analogous semantics.
- Data points to Enectiva [Create a new data point](https://apidocs.enectiva.cz/create-a-new-data-point-19188097e0.md): This endpoint enables clients to add new data points in custom data series to Enectiva. Each data point is sent in a separate HTTP request. There's no recommended frequency of data points sent because it depends on the time series, but too frequent requests might lead to rate limiting (429).
- Data points to Enectiva [Delete a data point by ID](https://apidocs.enectiva.cz/delete-a-data-point-by-id-20879935e0.md): This endpoint allows to delete a previously created data point based on its ID. The ID is sent in the response to the [creation request](apidog://link/endpoint/19188097).
- Data points to Enectiva [Delete a data point by time](https://apidocs.enectiva.cz/delete-a-data-point-by-time-20879936e0.md): This endpoint allows to delete a previously created data point based on the data series identification + data point time. The `time` field must conform to format defined in RFC3339 and must be truncated to whole seconds to be matched.
- Profiles to Enectiva [Latest profile](https://apidocs.enectiva.cz/latest-profile-19188100e0.md): Latest profile endpoint enables clients to get the latest imported profile for the given meter. It either returns the latest profile (even if marked as suspicious) with 200 or a 404 error when the given meter has no profiles stored.
- Profiles to Enectiva [Create a new/update an existing profile](https://apidocs.enectiva.cz/create-a-newupdate-an-existing-profile-19188099e0.md): This endpoint enables clients to add new profiles or update existing ones in Enectiva. Each profile is sent in a separate HTTP request. Sending profiles from multiple servers might hit rate limiting limits.
- Profiles to Enectiva [Delete a profile by ID](https://apidocs.enectiva.cz/delete-a-profile-by-id-20094713e0.md): This endpoint enables clients to remove an existing profile identified by profile ID. Each profile to delete is sent in a separate HTTP request. Sending profiles to delete from multiple servers might hit rate limiting limits.
- Profiles to Enectiva [Delete a profile by time range](https://apidocs.enectiva.cz/delete-a-profile-by-time-range-20094712e0.md): This endpoint enables clients to remove a profile selected by the combination of `importId`, `suit` and a time range. Each profile to delete is sent in a separate HTTP request. Sending profiles to delete from multiple servers might hit rate limiting limits.
- Readings to Enectiva [Latest reading](https://apidocs.enectiva.cz/latest-reading-19188102e0.md): Latest reading endpoint enables clients to get the latest imported reading for the given meter. It either returns the latest reading (even if marked as suspicious) with 200 or a 404 error when the given meter has no readings stored.
- Readings to Enectiva [Create a new reading](https://apidocs.enectiva.cz/create-a-new-reading-19188101e0.md): This endpoint enables clients to add new readings to Enectiva. Each reading is sent in a separate HTTP request. The client can send the readings with any frequency but there really is no point in sending more than one reading per minute per meter. Sending readings from multiple servers might hit rate limiting limits.
- Readings to Enectiva [Delete a reading by ID](https://apidocs.enectiva.cz/delete-a-reading-by-id-20879937e0.md): This endpoint allows to delete a previously created reading based on its ID. The ID is sent in the response to the [creation request](apidog://link/endpoint/19188101).
- Readings to Enectiva [Delete a reading by time](https://apidocs.enectiva.cz/delete-a-reading-by-time-20879938e0.md): This endpoint allows to delete a previously created reading based on the meter identification + reading time. The `time` field must conform to format defined in RFC3339 and must be truncated to whole seconds to be matched.
- Entities from Enectiva [List entities](https://apidocs.enectiva.cz/list-entities-20950408e0.md): This action allows to list entities of a specific customer.
- Entities from Enectiva [Entity](https://apidocs.enectiva.cz/entity-19188096e0.md): This action allows to fetch details of an entity.
- Readings from Enectiva [List readings of a meter](https://apidocs.enectiva.cz/list-readings-of-a-meter-19188106e0.md): This action allows to list readings of a single meter. Only valid and fully processed readings are included. Values are in the default unit of the corresponding energy. The values can be [sorted](apidog://link/pages/1363538#sort-options), the default order is chronological.
- Meters from Enectiva [List meters](https://apidocs.enectiva.cz/list-meters-19188103e0.md): This action allows to list meters of a specific customer. Only active meters are returned by default and deactivated meters can be included using the proper query parameter (include_deactivated). Virtual meters are not included.
- Meters from Enectiva [Meter](https://apidocs.enectiva.cz/meter-19188104e0.md): This action allows to the details of a meter.
- Received energy invoices [Create a new invoice](https://apidocs.enectiva.cz/create-a-new-invoice-19188105e0.md): This endpoint enables clients to add invoices for energy use to Enectiva. Each invoice is created in a separate HTTP request.