Skip to content

Cookie preferences

We use cookies for our own analytics, to see how our campaigns perform and, if you allow it, to load content from other services such as the Google site search. We never sell your data. Necessary cookies keep the site working and cannot be switched off. See our Cookie Policy for details and our Privacy Policy for how we handle personal data.

Security, load balancing and remembering your cookie choice.

Show us which pages people read, how they find the site and where they get stuck, so we can improve it (Google Analytics, Microsoft Clarity).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, LinkedIn, Meta, partner program). We do not use these cookies to build advertising profiles.

Load the site search from Google when you use it. Google sets its own cookies and shows ads in the search results.

© 2026 The ThingsBoard Authors
180 Try for free

ThingsBoard Cloud

Choose your data region

Your data stays in the region you choose, for residency and compliance. No credit card required.

Rather run it yourself? Install on your own servers

REST API

ThingsBoard Edge runs the same REST API server as ThingsBoard CE. Most endpoints are identical — Edge adds two controllers specific to edge instance management: edge-controller and edge-event-controller.

Access the interactive API reference on your Edge instance at:

http://localhost:8080/swagger-ui.html

If you are already logged into the ThingsBoard Edge UI, Swagger UI authenticates automatically using your session.

Pass the API key in the X-Authorization header:

X-Authorization: ApiKey YOUR_API_KEY_VALUE

API keys are long-lived, require no login, and can be revoked through the ThingsBoard Edge UI.

Obtain an access token by sending credentials to the login endpoint:

Terminal window
curl -X POST -H 'Content-Type: application/json' \
-d '{"username":"[email protected]", "password":"tenant"}' \
'http://localhost:8080/api/auth/login'

Response:

{"token":"YOUR_JWT_TOKEN", "refreshToken":"YOUR_JWT_REFRESH_TOKEN"}

Use the token in subsequent requests:

X-Authorization: Bearer YOUR_JWT_TOKEN

Access tokens are valid for 2.5 hours; refresh tokens for one week.

The Attributes API, Time Series API, and RPC API work identically to CE — the same request paths, parameters, and response formats. For full examples and parameter references, see the CE REST API reference.

For the full list of available controllers grouped by category, see the Controller Reference.