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

Tibber Devices API

IoT devices linked to a home, exposed across vehicles, chargers, thermostats, inverters, and energy systems.

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

This API exposes 3 JSON Schema definitions.

Tagged areas include Devices. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a changelog, and 3 JSON Schemas.

This API exposes 2 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version v1.

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

2 operations 2 paths 1 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.tibber.com/v1-beta/gql
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Tibber Devices API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 11 scopes. By default, every request must be authenticated.

  • oauth2 — OAuth 2.0 Authorization Code Flow with optional PKCE.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Devices 2

IoT devices linked to a home, exposed across vehicles, chargers, thermostats, inverters, and energy systems.

GET
/v1/homes/{homeId}/devices
List Devices For Home
listDevicesForHome 1 param → 200401403404429
GET
/v1/homes/{homeId}/devices/{deviceId}
Get Device
getDevice 2 params → 200404429

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Device (8 properties). Each schema is shown below with its type and property counts.

Device
object
8 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tibber-devices-api-openapi.yml Raw ↑

Other APIs Tibber publishes across the network.

Tibber GraphQL API
Tibber History API
Tibber Homes API
Where this information came from

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