Enectiva REST API - Librarian
HomeEnectivaUser ManualEnerfis
HomeEnectivaUser ManualEnerfis
  1. Profiles to 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. Profiles to Enectiva

Latest profile

GET
https://api.enectiva.cz//import/profiles/{customerId}/{importId}/{suit}/latest
Last modified:2025-09-03 14:58:29
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.
Any token allowed to add profiles is able to read the latest profile as well. The purpose is to minimize the number of requests to Librarian. Clients should keep track of profiles sent to Librarian on their own. However, if they, for some reason, lose track, the preferred course of action is to use this endpoint rather than to send a series of profiles that have been sent earlier. Duplicate requests result in 409 responses.
This endpoint requires an import token, not an access token.

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: No token URL is provided. Use "Import token" from the Auth URL
or
Path 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//import/profiles////latest' \
--header 'Accept: application/vnd.api+json' \
--header 'Authorization: Bearer <token>'

Responses

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

Example
{
    "data": {
        "attributes": {
            "customer_uuid": "11e7e767-6f74-4994-b607-158ff7f7445e",
            "from": "2015-11-18T09:54:23+01:00",
            "import_id": "40AABB_007",
            "suit": "default",
            "to": "2015-11-18T09:59:23+01:00",
            "unit": "kW",
            "value": 123456.78
        },
        "id": "1",
        "type": "profiles"
    }
}
🟠401Unauthorized
🟠403Forbidden
🟠404Record Not Found
🟠406Not Acceptable
🟠429Too Many Requests
🔴500Server Error
Modified at 2025-09-03 14:58:29
Previous
Delete a data point by time
Next
Create a new/update an existing profile
Built with