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

ThingsBoard telemetry-controller API

Telemetry

ThingsBoard telemetry-controller API is one of 58 APIs that ThingsBoard publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 11 JSON Schema definitions.

Tagged areas include telemetry-controller. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 11 JSON Schemas.

This API exposes 14 operations across 12 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 4.3.0.3DEMO.

Requests are made against 2 base URLs: https://demo.thingsboard.io, http://localhost:8080.

14 operations 12 paths 1 schemas 3 DELETE6 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4.3.0.3DEMO
Servers
https://demo.thingsboard.io
http://localhost:8080
Authentication
HTTP Loginpassword, API Key
License
Resource Areas
1

Authentication & Security 2

ThingsBoard telemetry-controller API declares 2 security schemes for authenticating requests. It uses HTTP loginpassword authentication (HTTP_login_form). An API key is passed in the header as X-Authorization (API_key_form).

  • HTTP_login_form — Enter Username / Password
  • API_key_form — Enter the API key value with 'ApiKey' prefix in format: ApiKey Example: ApiKey tb5te51SkLRYpjGrujUGwqkjFvooWBlQpVe2An2Dr3w13wjfxDW NOTE: Use only ONE authentic…

Paths & Operations 14

Across 12 paths, the API surfaces 14 operations — 3 DELETE, 6 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

telemetry-controller 14

Telemetry

POST
/api/plugins/telemetry/{entityType}/{entityId}/{scope}
Save Entity Attributes (saveEntityAttributesV1)
saveEntityAttributesV1 3 params body → 200400401500
DELETE
/api/plugins/telemetry/{entityType}/{entityId}/{scope}
Delete Entity Attributes (deleteEntityAttributes)
deleteEntityAttributes 5 params → 200400401500
POST
/api/plugins/telemetry/{entityType}/{entityId}/timeseries/{scope}
Save or Update Time Series Data (saveEntityTelemetry)
saveEntityTelemetry 3 params body → 200400401500
POST
/api/plugins/telemetry/{entityType}/{entityId}/timeseries/{scope}/{ttl}
Save or Update Time Series Data with TTL (saveEntityTelemetryWithTTL)
saveEntityTelemetryWithTTL 4 params body → 200400401500
POST
/api/plugins/telemetry/{entityType}/{entityId}/attributes/{scope}
Save Entity Attributes (saveEntityAttributesV2)
saveEntityAttributesV2 3 params body → 200400401500
POST
/api/plugins/telemetry/{deviceId}/{scope}
Save Device Attributes (saveDeviceAttributes)
saveDeviceAttributes 2 params body → 200400401500
DELETE
/api/plugins/telemetry/{deviceId}/{scope}
Delete Device Attributes (deleteDeviceAttributes)
deleteDeviceAttributes 4 params → 200400401500
GET
/api/plugins/telemetry/{entityType}/{entityId}/values/timeseries
Get Time Series Data (getTimeseries)
getLatestTimeseries 13 params → 200
GET
/api/plugins/telemetry/{entityType}/{entityId}/values/attributes
Get Attributes (getAttributes)
getAttributes 4 params → 200
GET
/api/plugins/telemetry/{entityType}/{entityId}/values/attributes/{scope}
Get Attributes by Scope (getAttributesByScope)
getAttributesByScope 5 params → 200
GET
/api/plugins/telemetry/{entityType}/{entityId}/keys/timeseries
Get Time Series Keys (getTimeseriesKeys)
getTimeseriesKeys 2 params → 200
GET
/api/plugins/telemetry/{entityType}/{entityId}/keys/attributes
Get All Attribute Keys (getAttributeKeys)
getAttributeKeys 2 params → 200
GET
/api/plugins/telemetry/{entityType}/{entityId}/keys/attributes/{scope}
Get All Attribute Keys by Scope (getAttributeKeysByScope)
getAttributeKeysByScope 3 params → 200
DELETE
/api/plugins/telemetry/{entityType}/{entityId}/timeseries/delete
Delete Entity Time Series Data (deleteEntityTimeseries)
deleteEntityTimeseries 9 params → 200400401500

Schemas 1

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

MultiValueMapStringString
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

thingsboard-telemetry-controller-api-openapi.yml Raw ↑

Other APIs ThingsBoard publishes across the network.

ThingsBoard admin-controller API
ThingsBoard ai-model-controller API
ThingsBoard alarm-comment-controller API
ThingsBoard alarm-controller API
ThingsBoard api-key-controller API
ThingsBoard asset-controller API
ThingsBoard asset-profile-controller API
ThingsBoard audit-log-controller API
ThingsBoard auth-controller API
ThingsBoard calculated-field-controller API
ThingsBoard component-descriptor-controller API
ThingsBoard customer-controller API
Where this information came from

This is an independent, third-party profile of ThingsBoard telemetry-controller 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.