ClearBlade API

Name: ClearBlade API API
Brand: ClearBlade API
Availability: InStock

★ Only Publicly Available SpecIOTDevice ManagementapiKey220 EndpointsREST

For Agents

Provision ClearBlade systems, register and update devices, run data collection queries, execute code services, and inspect message history. Useful for industrial IoT fleet management and edge orchestration.

Quickstart

Get started with ClearBlade API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"register a device in ClearBlade"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with ClearBlade API API.

Provision and configure ClearBlade systems and developer accounts

Manage data collections including create, update, and delete operations

Trigger and inspect server-side code services and triggers

Rotate device authentication keys for security compliance

GET STARTED

Start building with ClearBlade API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for ClearBlade API, keeping it validated and agent-ready.

ClearBlade is an industrial IoT platform, and its REST API exposes the platform's full operational surface across systems, devices, collections, code services, message-passing, and developer administration. With over 220 endpoints, the API covers everything from provisioning a new system and registering devices to running data queries, sending MQTT messages, and rotating device keys. Operations are grouped under admin, codes, data, devices, edges, and message-history namespaces, reflecting the platform's multi-tenant edge-and-cloud architecture. It is designed for industrial operators, OEMs, and IoT solution builders who need full programmatic control over a fleet.

Use Cases

Patterns agents use ClearBlade API API for, with concrete tasks.

★ Bulk device provisioning for a new deployment

When rolling out a new IoT deployment, operations teams need to register hundreds or thousands of devices into the ClearBlade system. POST /admin/devices/{systemKey}/{name} creates devices and POST /admin/devices/keys/{systemKey}/{deviceName} provisions their rotating authentication keys. Running these in batches against the platform avoids manually clicking through the console for each device and keeps the device registry as the canonical source.

For each row in the device manifest CSV, call POST /admin/devices/{systemKey}/{name} then POST /admin/devices/keys/{systemKey}/{deviceName} to create rotating keys

Audit log export for compliance reporting

Compliance teams in regulated industries need device and platform audit data exported into their SIEM. GET /admin/audit and GET /admin/audit/{systemKey} return the audit log for a system, with /count variants for pagination planning. Scheduling this nightly into a SIEM gives auditors a continuous record without needing console access to ClearBlade.

Each night, call GET /admin/audit/{systemKey} for the production system, paginate based on the /count endpoint, and forward the records to the Splunk HEC endpoint

Stale device cleanup

Fleets accumulate stale devices that no longer report telemetry. GET /admin/devices/{systemKey} with a query filter identifies devices that have not connected recently, and DELETE /admin/devices/{systemKey} removes them in bulk. Running this monthly keeps device counts and license usage aligned with the active fleet.

Find all devices in the production system with last_active older than 90 days using GET /admin/devices/{systemKey}, then call DELETE /admin/devices/{systemKey} with the matching query

Code service trigger inspection

When a code service misfires, debugging often starts with checking which triggers reference it and what audit entries describe its recent runs. The admin endpoints expose service-trigger relationships and the audit endpoints expose execution history. Pulling both together gives a clear view of which triggers fire which services and how often they error.

List the code services registered for system 'prod-system' and pull their recent audit entries via GET /admin/audit/{systemKey} to identify the failing trigger

AI agent integration via Jentic

An IoT operations agent uses Jentic to discover ClearBlade endpoints by intent and orchestrate fleet operations from natural-language requests. Because the API key auth is held in the Jentic vault, the agent can be deployed to operations engineers without distributing platform credentials. The same agent can register devices, rotate keys, and query audit logs by re-running searches on different intents.

Receive 'rotate keys for device gateway-42' from chat, search Jentic for ClearBlade device key rotation, and execute POST /admin/devices/keys/{systemKey}/{deviceName} for that device

Key Endpoints

220 endpoints — clearblade is an industrial iot platform, and its rest api exposes the platform's full operational surface across systems, devices, collections, code services, message-passing, and developer administration.

METHOD

PATH

DESCRIPTION

POST

/admin/devices/{systemKey}/{name}

Create a device in a system

GET

/admin/devices/{systemKey}

Query devices in a system

POST

/admin/devices/keys/{systemKey}/{deviceName}

Create rotating keys for a device

GET

/admin/audit/{systemKey}

Get system audit information

POST

/admin/auth

Authenticate developer credentials

POST

/admin/collectionmanagement

Create a data collection

GET

/admin/allsystems

List all systems

DELETE

/admin/devices/{systemKey}

Delete devices using a query

POST

/admin/devices/{systemKey}/{name}

Create a device in a system

GET

/admin/devices/{systemKey}

Query devices in a system

POST

/admin/devices/keys/{systemKey}/{deviceName}

Create rotating keys for a device

GET

/admin/audit/{systemKey}

Get system audit information

POST

/admin/auth

Authenticate developer credentials

Why though Jentic?

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

Credential isolation

ClearBlade developer credentials and per-system API keys are stored encrypted in the Jentic vault. Agents call the 220-endpoint surface through Jentic without ever holding the credentials, which is critical when an agent operates across multiple systems on behalf of different operators.

Intent-based discovery

Agents query Jentic with intents like 'register an IoT device' or 'rotate device keys' and Jentic returns the matching ClearBlade operation along with its input schema, so the right endpoint is selected from a 220-endpoint surface without browsing the docs.

Time to first call

Direct ClearBlade integration: 3-7 days for auth, system bootstrapping, device registration flows, and audit pipeline wiring. Through Jentic: a few hours — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Particle API

Connected device platform with strong cellular IoT story

Choose Particle when cellular-first connectivity matters; choose ClearBlade for industrial deployments needing edge-and-cloud topology

Complementary

Samsara API

Connected operations and fleet telematics platform

Pair Samsara with ClearBlade when fleet vehicle telematics are needed alongside generic industrial device management

Alternative

Adafruit IO API

Hobbyist and prototyping IoT platform

Use Adafruit IO for prototypes and educational projects; ClearBlade is the right choice for production industrial deployments

FAQs

Specific to using ClearBlade API API through Jentic.

What authentication does the ClearBlade API use?

ClearBlade uses an API key passed in request headers, with developer-level authentication issued via POST /admin/auth and verified via POST /admin/checkauth. The OpenAPI spec does not declare the security scheme inline, so the auth header is configured at the request level. Through Jentic, both the platform credentials and per-system tokens are stored in the encrypted vault.

Can I register devices in bulk through the ClearBlade API?

Yes. POST /admin/devices/{systemKey}/{name} creates a single device, and the corresponding GET, PUT, and DELETE on /admin/devices/{systemKey} accept queries for bulk operations. For new deployments, you typically iterate through your device manifest and call the create endpoint for each entry.

How do I rotate device authentication keys?

Call POST /admin/devices/keys/{systemKey}/{deviceName} to create a new rotating key, and DELETE /admin/devices/keys/{systemKey}/{deviceName} to revoke an existing one. This is the standard pattern for periodic key rotation in regulated IoT deployments.

How do I export ClearBlade audit logs through Jentic?

Install the SDK with pip install jentic, search Jentic for 'get clearblade audit logs', load the schema, and execute against GET /admin/audit/{systemKey}. Use the matching /count endpoint to plan pagination, then forward records to your SIEM.

Does the ClearBlade API expose MQTT message history?

Yes. The platform stores MQTT topic and message history that can be queried through admin endpoints, alongside the data collection endpoints for telemetry storage. This gives you both the realtime broker view and the historical record without leaving the platform.

Are ClearBlade systems multi-tenant?

Yes. Each system has its own systemKey and admin operations are scoped to that key. Developers with access to multiple systems can iterate via GET /admin/allsystems and act on each system in turn, which is the standard fan-out pattern for managed-service operators.