Tibber Devices API

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

Operations 2

GET /v1/homes/{homeId}/devices List Devices For Home #
GET /v1/homes/{homeId}/devices/{deviceId} Get Device #

Documentation

Specifications

Schemas & Data

Other Resources

🔗
Scopes
https://data-api.tibber.com/docs/scopes/
🔗
Sandbox
https://data-api.tibber.com/playground/
🔗
ChangeLog
https://data-api.tibber.com/docs/changelog/
🔗
FAQ
https://data-api.tibber.com/docs/further-reading/faq/
🔗
Console
https://data-api.tibber.com/clients/manage/
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/tibber/refs/heads/main/examples/tibber-list-homes-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/tibber/refs/heads/main/examples/tibber-device-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/tibber/refs/heads/main/examples/tibber-device-history-example.json
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/tibber/refs/heads/main/apis.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/tibber/refs/heads/main/arazzo/tibber-consumption-report-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/tibber/refs/heads/main/arazzo/tibber-current-price-by-home-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/tibber/refs/heads/main/arazzo/tibber-inspect-connected-device-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/tibber/refs/heads/main/arazzo/tibber-price-alert-push-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/tibber/refs/heads/main/arazzo/tibber-production-report-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/tibber/refs/heads/main/arazzo/tibber-pull-device-history-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/tibber/refs/heads/main/arazzo/tibber-realtime-power-readiness-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/tibber/refs/heads/main/arazzo/tibber-submit-meter-reading-workflow.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/tibber-devices-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

tibber-devices-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Tibber Data Devices API
  description: Tibber's modern OAuth 2.0 REST API exposing third-party connected IoT devices and their historical time series.
  version: v1
  contact:
    name: Tibber Data API
    url: https://data-api.tibber.com/docs/
servers:
- url: https://data-api.tibber.com
  description: Tibber Data API (production)
security:
- oauth2: []
tags:
- name: Devices
  description: IoT devices linked to a home, exposed across vehicles, chargers, thermostats, inverters, and energy systems.
paths:
  /v1/homes/{homeId}/devices:
    get:
      tags:
      - Devices
      summary: List Devices For Home
      operationId: listDevicesForHome
      description: List all linked devices in the given home. Devices only appear when the token carries the matching category scope (for example, `data-api-vehicles-read` for vehicles or `data-api-thermostats-read` for thermostats and heat pumps).
      parameters:
      - in: path
        name: homeId
        required: true
        schema:
          type: string
          format: uuid
      responses:
        '200':
          description: Array of devices for the home.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Device'
        '401':
          description: Missing or expired access token.
        '403':
          description: Token lacks a category scope.
        '404':
          description: Home not found or not accessible to caller.
        '429':
          description: Rate limit exceeded.
  /v1/homes/{homeId}/devices/{deviceId}:
    get:
      tags:
      - Devices
      summary: Get Device
      operationId: getDevice
      description: Return identity, attributes, capabilities, and `supportedHistory` for one device.
      parameters:
      - in: path
        name: homeId
        required: true
        schema:
          type: string
          format: uuid
      - in: path
        name: deviceId
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Device representation.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Device'
        '404':
          description: Device not found.
        '429':
          description: Rate limit exceeded.
components:
  schemas:
    Device:
      type: object
      required:
      - id
      - category
      properties:
        id:
          type: string
        category:
          type: string
          enum:
          - vehicle
          - charger
          - thermostat
          - inverter
          - energySystem
        vendor:
          type: string
        model:
          type: string
        attributes:
          type: object
          additionalProperties: true
        capabilities:
          type: array
          items:
            type: string
        supportedHistory:
          type: array
          items:
            type: string
            enum:
            - quarterHour
            - hour
            - day
            - month
        maxRetentionDays:
          type: integer
  securitySchemes:
    oauth2:
      type: oauth2
      description: OAuth 2.0 Authorization Code Flow with optional PKCE.
      flows:
        authorizationCode:
          authorizationUrl: https://thewall.tibber.com/connect/authorize
          tokenUrl: https://thewall.tibber.com/connect/token
          refreshUrl: https://thewall.tibber.com/connect/token
          scopes:
            openid: OpenID identity.
            profile: User profile.
            email: User email.
            offline_access: Issue refresh tokens.
            data-api-user-read: Basic user context (required baseline).
            data-api-homes-read: List the user's homes.
            data-api-vehicles-read: Read connected electric vehicles.
            data-api-chargers-read: Read EV chargers and EVSE equipment.
            data-api-thermostats-read: Read thermostats, heat pumps, and space heaters.
            data-api-energy-systems-read: Read home batteries and hybrid systems.
            data-api-inverters-read: Read solar inverters.