How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Eliq Intelligence API

The Eliq Intelligence API provides customer-level analytics designed for utility service, operations, and growth teams. It supports customer segmentation, behavioral classification, and personalized recommendations derived from consumption history, weather, tariffs, and disaggregation models. Access to the Intelligence API is granted on request.

Eliq Intelligence API is one of 4 APIs that Eliq publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Intelligence, Segmentation, Energy, and Utilities. The published artifact set on APIs.io includes API documentation, an OpenAPI specification, and an API reference.

This API exposes 10 operations across 10 paths, organized into 3 resource areas, and defines 35 schemas. It is described by OpenAPI 3.0.1, at version 1.0.0.

Requests are made against a single base URL, https://eliq.intelligence-api.eliq.com.

10 operations 10 paths 35 schemas 6 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0.0
Base URL
https://eliq.intelligence-api.eliq.com
Authentication
HTTP Bearer
Contact
Resource Areas
3

Authentication & Security 1

Eliq Intelligence API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer). By default, every request must be authenticated.

  • Bearer — Enter JWT Bearer token only

Paths & Operations 10

Across 10 paths, the API surfaces 10 operations — 6 GET, 4 POST. They span 3 resource areas: Dashboards, Info, LocationSegmentation. Each is listed below with its method, path, parameters, and response codes.

Dashboards 1
POST
/dashboards/{dashboard_id}/token
Mint a user-scoped token for embedding a dashboard with @databricks/aibi-client
1 param → 200401404
Info 3
GET
/info/auth
Get Entra authentication information for the application
→ 200
GET
/info/me
Get information about the current user
→ 200
GET
/info/configuration
Get the Intelligence API configuration for the client
→ 200404
LocationSegmentation 6
POST
/locations/segmentation/filter
Filters Location Segmentation data.
body → 200400
POST
/locations/segmentation/export/create
Creates an export job to export all segments to a CSV file.
body → 201400
GET
/locations/segmentation/export/{jobId}
Gets the export job.
1 param → 200400
GET
/locations/segmentation/export/{jobId}/download
Downloads the file containing exported locations.
1 param → 200400
GET
/locations/segmentation/filter/tariffValues
Get tariff filter options. Returns all possible tariffIds for the client and their names.
→ 200400
POST
/locations/segmentation/map
1 param body → 200400

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are FilterResponseItem (10 properties), MapLocationDto (8 properties), Summary (8 properties), DashboardEmbedTokenResult (5 properties). Each schema is shown below with its type and property counts.

AssetKind
string
Assets
object
5 properties
AuthInfoResult
object
Authorization information for the application
2 properties 2 required
Battery
object
1 property
DashboardConfigurationItem
object
A published DataBricks dashboard the client is allowed to embed
3 properties
DashboardEmbedTokenResult
object
Everything the frontend needs to embed a dashboard with @databricks/aibi-client
5 properties 5 required
DashboardsConfiguration
object
DataBricks dashboards available for embedding in the application
2 properties
ElectricVehicle
object
3 properties
ErrorDetails
object
2 properties 2 required
ExportJob
object
2 properties
ExportJobStatus
string
FilterRequest
object
1 property
FilterRequestAsset
object
3 properties 1 required
FilterRequestAssetProperty
object
3 properties
FilterResponse
object
3 properties
FilterResponseItem
object
10 properties
HeatingDetails
object
4 properties
HeatingFuelFlags
object
2 properties
IntelligenceApiConfiguration
object
2 properties
JsonNode
object
3 properties
JsonNodeOptions
object
1 property
MapLocationDto
object
8 properties
MapSegmentationResponseDto
object
1 property
MyInfoResult
object
Information about the active user
2 properties 2 required
Operator
string
PagedFilterRequest
object
2 properties
Paging
object
3 properties
PagingRequest
object
2 properties
PvDetails
object
4 properties
PvDetectionSource
string
Summary
object
8 properties
TariffCount
object
2 properties
TariffFilterOptions
object
2 properties
TariffSummary
object
4 properties
Tariffs
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eliq-intelligence-api-openapi.json Raw ↑

Other APIs Eliq publishes across the network.

Eliq Auth API
Eliq Data Management API
Eliq Insights API
Where this information came from

This is an independent, third-party profile of Eliq Intelligence 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.