Enectiva REST API - Librarian
HomeEnectivaUser ManualEnerfis
HomeEnectivaUser ManualEnerfis
  1. Readings from Enectiva
  • Introduction
  • Access tokens
    • Create a new access token
      POST
  • Data points from Enectiva
    • List data points of a data series
      GET
  • Deltas
    • Introduction to Deltas
    • List monthly deltas of an entity
      GET
    • List monthly deltas of a meter
      GET
    • List monthly deltas of a virtual meter
      GET
  • Data points to Enectiva
    • Latest data point
      GET
    • Create a new data point
      POST
    • Delete a data point by ID
      DELETE
    • Delete a data point by time
      DELETE
  • Profiles to Enectiva
    • Latest profile
      GET
    • Create a new/update an existing profile
      POST
    • Delete a profile by ID
      DELETE
    • Delete a profile by time range
      DELETE
  • Readings to Enectiva
    • Latest reading
      GET
    • Create a new reading
      POST
    • Delete a reading by ID
      DELETE
    • Delete a reading by time
      DELETE
  • Entities from Enectiva
    • List entities
      GET
    • Entity
      GET
  • Readings from Enectiva
    • List readings of a meter
      GET
  • Meters from Enectiva
    • List meters
    • Meter
  • Received energy invoices
    • Create a new invoice
  1. Readings from Enectiva

List readings of a meter

GET
https://api.enectiva.cz//meters/{meterIdentification}/readings
Last modified:2025-09-24 12:22:48
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, the default order is chronological.
The number of returned records is by default limited to 1000, see Limit & pagination for details. If more records satisfy your temporal filter, you can either keep the filter and paginate over the result set using the page parameter, or narrow down the filter with each request.
The required scope is readings.
If you do not specify a unit, the readings will be returned in the unit configured in Enectiva. You can request readings in an alternative unit. The available units depend on the energy measured and match the units in the application. Supplying an invalid unit returns an error and lists the applicable units.

Request

Authorization
OAuth 2.0
Authorization Code
Add the parameter
Authorization
to Headers
,whose value is to concatenate the Token after the Bearer.
Example:
Authorization: Bearer ********************
Authorize URL: https://app.enectiva.cz/en/api/dashboard
Token URL: /access_tokens
or
Path Params

Query Params

Header Params

Request Code Samples

Shell
JavaScript
Java
Swift
Go
PHP
Python
HTTP
C
C#
Objective-C
Ruby
OCaml
Dart
R
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request GET 'https://api.enectiva.cz//meters//readings?filter&unit&sort&limit&page' \
--header 'Accept: application/vnd.api+json' \
--header 'Authorization: Bearer <token>'

Responses

🟢200OK
application/vnd.api+json
OK
Body

Examples
{
  "data": [
    {
      "id": "5666368",
      "attributes": {
        "time": "2018-01-01T00:00:00.000Z",
        "state": 0,
        "unit": "kWh"
      },
      "type": "readings"
    },
    {
      "id": "5666365",
      "attributes": {
        "time": "2018-12-31T23:59:00.000Z",
        "state": 1200,
        "unit": "kWh"
      },
      "type": "readings"
    },
    {
      "id": "5657622",
      "attributes": {
        "time": "2019-09-30T12:46:00.000Z",
        "state": 10000,
        "unit": "kWh"
      },
      "type": "readings"
    }
  ]
}
🟠400Bad Request
🟠401Unauthorized
🟠403Forbidden
🟠404Record Not Found
🟠406Not Acceptable
🟠409Conflict
🟠429Too Many Requests
🔴500Server Error
Modified at 2025-09-24 12:22:48
Previous
Entity
Next
List meters
Built with