The Eliq Data Management API ingests and manages customer, location, and meter data inside the Eliq system. Clients use it to provision users and locations, post energy consumption readings, attach metadata such as tariffs and dwelling information, and keep the dataset that powers the Insights API up to date.
Eliq Data Management API is one of 4 APIs that Eliq publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Data Management, Energy, and Utilities. The published artifact set on APIs.io includes API documentation, an OpenAPI specification, and an API reference.
This API exposes
78 operations
across 43 paths,
organized into 18 resource areas,
and defines 61 schemas.
It is described by OpenAPI 3.0.1, at version 1.5.2.
Requests are made against a single base URL, https://eliq.data-management-api.eliq.com/integration/api/v1.
78 operations43 paths61 schemas20 DELETE36 GET1 PATCH14 POST7 PUT
Metadata
The identity and technical contract details declared by the specification.
Across 43 paths, the API surfaces 78 operations — 20 DELETE, 36 GET, 1 PATCH, 14 POST, 7 PUT. They span 18 resource areas, including Client details, Jobs, Location price formulas, Location profile, Location, Location home profile, Meter Price Formulas, Meter, and 10 more. Each is listed below with its method, path, parameters, and response codes.
Client details 1
GET
/client-details/available-languages
Gets available languages for the users
get-availablelanguages→ 200409500
Jobs 8
POST
/jobs/{entity}/{operation}
Create job based on entity and operation and provided file
create-job2 params→ 200400404500
GET
/jobs/{jobId}/cancel
Cancel job before it is finished by job id
cancel-job1 param→ 202400500
GET
/jobs
Get jobs based on job state, id or name reference.
get-jobs4 params→ 200400500
GET
/jobs/{jobId}
Get Job details by job id
get-job1 param→ 200404500
GET
/jobs/{jobId}/failures
Get errors and details from job.
get-job-failures3 params→ 200404500
GET
/jobs/{jobId}/content
Get Job content - the .ndjson file provided as the input when the Job was created.
get-job-content1 param→ 200404500
GET
/jobs/{jobId}/result
Get Job result. Export include result object containing exported details.
get-job-result1 param→ 200404500
GET
/jobs/{jobId}/result/{page}
Get Job result. Export include result object containing exported details.
The contract defines 61 schemas that model the data the API accepts and returns. The most detailed are Meter (14 properties), JobEntry (12 properties), Location (10 properties), LocationProfileSetting (9 properties). Each schema is shown below with its type and property counts.
AcceptedResult
object
6 properties
Block
object
7 properties
CapacityTariff
object
3 properties
Charge
object
4 properties
DeviceMaxDemand
object
3 properties
DeviceMaxDemandLimit
object
4 properties
DtoLink
object
3 properties
DtoLinkTarget
string
Element
object
4 properties
EnergyDailyData
object
5 properties
EnergyHighResolutionData
object
4 properties
EnergyMonthlyData
object
8 properties
ErrorDetails
object
3 properties2 required
FileRowError
object
2 properties
Fixed
object
1 property
HomeProfileProperty
object
3 properties
IOutputFormatter
object
Interval
object
2 properties
JobEntry
object
12 properties
JobEntryStateType
string
JobFailedRow
object
3 properties
JobOperationType
string
JobResultRow
object
4 properties
JobType
string
Location
object
10 properties
LocationAddress
object
4 properties
LocationGeo
object
2 properties
LocationPriceFormula
object
9 properties
LocationProfileDataType
string
LocationProfilePossibleValue
object
2 properties
LocationProfilePropertyRequirement
object
2 properties
LocationProfileSelectedValue
object
3 properties
LocationProfileSetting
object
9 properties8 required
LocationProfileSettings
object
2 properties2 required
LocationProfileTag
string
LocationProfileType
object
1 property
LocationProfileValueRequest
object
3 properties2 required
LocationProfileValueResponse
object
4 properties2 required
LocationPropertyLimit
object
3 properties
Meter
object
14 properties
NoContentResult
object
1 property
NonSmartMeterReadDto
object
6 properties
NonSmartRegisterDto
object
2 properties
NotificationDto
object
4 properties
NotificationType
string
OkObjectResult
object
5 properties
PatchLocationProfileRequestModel
object
2 properties
PortfolioAccount
object
3 properties1 required
PortfolioGroup
object
8 properties
PortfolioGroupAddDto
object
3 properties
PortfolioGroupStatus
string
PortfolioLocation
object
3 properties1 required
PortfolioUser
object
6 properties2 required
PortfolioUserRole
string
PriceFormula
object
7 properties
ProfileType
string
Register
object
3 properties
SpotPrice
object
4 properties
Tou
object
4 properties
UnitRate
object
6 properties
User
object
8 properties
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Eliq Data Management API, published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.