ThingsBoard REST API

Name: ThingsBoard REST API
Brand: ThingsBoard REST API
Availability: InStock

✓ Official Vendor SpecIOTDevice ManagementapiKey, loginPassword496 EndpointsREST

For Agents

Programmatically login method to get user jwt token data, refresh user jwt token data. Covers 496 operations with apiKey, loginPassword authentication.

Install Jentic One Beta

Connect the ThingsBoard REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ThingsBoard REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ThingsBoard REST API.

Refresh user JWT token data

Save user settings (saveUserSettings)

Get user settings (getUserSettings)

GET STARTED

Start building with ThingsBoard REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ThingsBoard REST API for, with concrete tasks.

★ IoT and Hardware Operations

Use the ThingsBoard REST API to perform iot operations programmatically. The API provides 496 endpoints covering core functionality including login method to get user jwt token data, refresh user jwt token data, save user settings (saveusersettings).

Call POST /api/auth/login to login method to get user jwt token data

Automated .Well Known Management

Automate .well known operations by combining multiple ThingsBoard REST API endpoints. Agents can refresh user jwt token data and then save user settings (saveusersettings) in a single workflow.

Call POST /api/auth/token to refresh user jwt token data, then verify the result

AI Agent Integration via Jentic

AI agents discover and call ThingsBoard REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, loginPassword tokens manually.

Search Jentic for 'login method to get user jwt token data', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

496 endpoints — thingsboard open-source iot platform rest api documentation.

METHOD

PATH

DESCRIPTION

POST

/api/auth/login

POST

/api/auth/token

Refresh user JWT token data

POST

/api/user/settings

Save user settings (saveUserSettings)

GET

/api/user/settings

Get user settings (getUserSettings)

PUT

/api/user/settings

Update user settings (saveUserSettings)

GET

/api/user/settings/{type}

Get user settings (getUserSettings)

PUT

/api/user/settings/{type}

Update user settings (saveUserSettings)

PUT

/api/resource/{id}/info

updateResourceInfo

POST

/api/auth/login

POST

/api/auth/token

Refresh user JWT token data

POST

/api/user/settings

Save user settings (saveUserSettings)

GET

/api/user/settings

Get user settings (getUserSettings)

PUT

/api/user/settings

Update user settings (saveUserSettings)

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ThingsBoard REST API apiKey, loginPassword credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'login method to get user jwt token data') and Jentic returns the matching ThingsBoard REST API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct ThingsBoard REST API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using ThingsBoard REST API through Jentic.

What authentication does the ThingsBoard REST API use?

The ThingsBoard REST API uses apiKey, loginPassword authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I login method to get user jwt token data with the ThingsBoard REST API?

Yes. Use the POST /api/auth/login endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the ThingsBoard REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I login method to get user jwt token data through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'login method to get user jwt token data'. Jentic returns the matching ThingsBoard REST API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the ThingsBoard REST API have?

The ThingsBoard REST API exposes 496 endpoints covering .well known, 2fa, admin operations.

ThingsBoard REST API

Connect the ThingsBoard REST API to your agent

Capabilities

Start building with ThingsBoard REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs