Blues Notehub API

Name: Blues Notehub API API
Brand: Blues Notehub API
Availability: InStock

★ Only Publicly Available SpecIOTDevice Managementbearer81 EndpointsREST

For Agents

Manage Blues Notecard cellular IoT devices end-to-end: provisioning, fleets, environment variables, event routing, firmware, and billing through Notehub.

Quickstart

Get started with Blues Notehub 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:
"disable a Notecard device in Notehub"

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

Capabilities

What an agent can do with Blues Notehub API API.

Provision, enable, and disable individual Notecard devices remotely

Push environment variables down to a project, fleet, or specific device

Read and write Notes — the per-device data records exchanged between firmware and cloud

Configure routes that forward incoming events to AWS, Azure, MQTT, or HTTP targets

GET STARTED

Start building with Blues Notehub API API

Explore with Jentic

View OpenAPI Spec

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

Jentic publishes the only available OpenAPI specification for Blues Notehub API, keeping it validated and agent-ready. This blues.io listing covers the broader 81-endpoint Notehub surface, including projects, products, fleets, devices, notes, events, routes, monitors, environment variables, firmware updates, billing accounts, and usage data. Notehub is the cloud counterpart to the Blues Notecard cellular module, and the API supports remote firmware delivery, per-device enable and disable, and full lifecycle management for cellular IoT deployments. Authentication uses Bearer tokens obtained from /oauth2/token.

Use Cases

Patterns agents use Blues Notehub API API for, with concrete tasks.

★ Remote firmware rollout

Push firmware updates to fielded Notecard devices through Notehub's firmware endpoints. Upload the firmware artifact, target a fleet or specific devices, and monitor rollout progress. The /v1/projects/{projectOrProductUID}/firmware endpoints handle artifact management and assignment, with Notehub coordinating delivery as devices check in. Suitable for OTA rollouts to remote and battery-constrained hardware where in-person updates are impractical.

Upload a firmware binary, then call the firmware assignment endpoint to target a fleet and confirm the rollout was created.

Per-device troubleshooting

Investigate a single misbehaving Notecard by pulling its events, environment variables, and current state. GET /v1/projects/{projectOrProductUID}/devices/{deviceUID} returns identity and last-seen, while POST /v1/projects/{projectOrProductUID}/devices/{deviceUID}/disable temporarily takes it out of the fleet. Re-enable via the corresponding POST .../enable endpoint after the issue is resolved.

Call GET /v1/projects/{projectOrProductUID}/devices/{deviceUID} for a flagged device, then POST /v1/projects/{projectOrProductUID}/devices/{deviceUID}/disable to take it offline pending investigation.

Environment-variable-driven feature flags

Roll out feature flags to fielded devices through scoped environment variables. Variables can be set at project, fleet, or device level, with the most specific scope winning. PUT /v1/projects/{projectOrProductUID}/devices/{deviceUID}/environment_variables targets one device; the fleet variant targets a group; the project variant becomes the default. Useful for staged rollouts of firmware behaviour without recompiling.

Call PUT /v1/projects/{projectOrProductUID}/devices/{deviceUID}/environment_variables with {beta_features: 'on'} to enable a beta build's flags on a single device.

Cellular data cost monitoring

Track cellular data consumption across a deployment by reading billing accounts and usage. GET /v1/billing-accounts lists accounts and limits, and per-project usage endpoints return event and byte counts. Useful for finance and operations teams who need to attribute Blues cellular costs back to specific projects or fleets.

Call GET /v1/billing-accounts and return each account's name, current period consumption, and hard limit.

AI agent IoT operations assistant

Let an AI agent take operational actions against a Blues fleet — pulling device status, disabling problem units, or rolling environment variables. The agent searches Jentic for the right Notehub operation by intent, loads the schema, and executes with the Bearer token held in the Jentic vault. Suitable for ops chatbots, customer support copilots, and on-call investigation agents.

Search Jentic for 'disable a Notecard device', load the schema, and execute it for the deviceUID flagged by upstream monitoring.

Key Endpoints

81 endpoints — jentic publishes the only available openapi specification for blues notehub api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/oauth2/token

Exchange a Personal Access Token for an OAuth bearer token

GET

/v1/projects/{projectOrProductUID}/devices

List devices in a project

POST

/v1/projects/{projectOrProductUID}/devices/{deviceUID}/disable

Disable a specific Notecard device

POST

/v1/projects/{projectOrProductUID}/devices/{deviceUID}/enable

Re-enable a disabled device

PUT

/v1/projects/{projectOrProductUID}/devices/{deviceUID}/environment_variables

Set per-device environment variables

POST

/v1/projects/{projectOrProductUID}/fleets

Create a fleet within a project

GET

/v1/billing-accounts

List billing accounts and usage

POST

/oauth2/token

Exchange a Personal Access Token for an OAuth bearer token

GET

/v1/projects/{projectOrProductUID}/devices

List devices in a project

POST

/v1/projects/{projectOrProductUID}/devices/{deviceUID}/disable

Disable a specific Notecard device

POST

/v1/projects/{projectOrProductUID}/devices/{deviceUID}/enable

Re-enable a disabled device

PUT

/v1/projects/{projectOrProductUID}/devices/{deviceUID}/environment_variables

Set per-device environment variables

Why though Jentic?

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

Credential isolation

Blues Personal Access Tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access, and the OAuth bearer token exchange via POST /oauth2/token happens automatically at execution time, so the agent never handles the raw PAT.

Intent-based discovery

Agents search by intent (e.g. 'disable a Notecard' or 'push a firmware update to a fleet') and Jentic returns the matching Notehub operation across the 81 endpoints with its input schema, so the agent can call the right path without browsing dev.blues.io.

Time to first call

Direct integration: 2-4 days for OAuth token exchange, project/fleet hierarchy mapping, firmware artifact handling, and route configuration. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Blues Notehub API

Sister Notehub listing covering the 72-endpoint core surface

Choose the blues entry for the smaller subset focused on project/fleet/device/routing; choose this entry when firmware or notes endpoints are required

Alternative

Blynk

IoT platform with mobile app and dashboards — alternative for Wi-Fi/BLE prosumer hardware

Choose Blynk for non-cellular hobbyist IoT with mobile app needs; choose Blues for cellular Notecard fleets

Complementary

Blueshift

Customer engagement platform — pair when IoT events should drive customer-facing notifications

Use when an agent must trigger a Blueshift email or push campaign in response to a Notehub event

FAQs

Specific to using Blues Notehub API API through Jentic.

Why is there no official OpenAPI spec for Blues Notehub API?

Blues publishes a Notehub API reference site but does not distribute a maintained OpenAPI 3 file. Jentic generates and maintains this spec so AI agents and developers can call Notehub via standard tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Blues Notehub API use?

Notehub uses HTTP Bearer authentication. Exchange a Personal Access Token for an OAuth bearer token via POST /oauth2/token, then pass it as Authorization: Bearer <token>. Through Jentic, the PAT is held in the encrypted vault and the OAuth exchange happens automatically at execution time.

Can I push firmware updates through this API?

Yes. Notehub exposes firmware management endpoints that let you upload an artifact and assign it to a fleet or specific devices. Devices fetch the update on their next check-in, and you can monitor rollout state via the firmware status endpoints.

What are the rate limits for the Blues Notehub API?

Notehub applies per-account rate limits not enumerated in the spec. Published guidance is to keep request volume under roughly 60 requests per minute per token; HTTP 429 responses include backoff hints. Higher limits are available for enterprise customers on request.

How do I disable a misbehaving device through Jentic?

Search Jentic for 'disable a Notecard device', load the schema for POST /v1/projects/{projectOrProductUID}/devices/{deviceUID}/disable, and execute it with the deviceUID. Install with pip install jentic and call await client.execute(ExecutionRequest(...)).

How is this listing different from the blues vendor entry?

Both expose the same Blues Notehub API. The blues.io listing covers the broader 81-endpoint surface including firmware, notes, and per-device enable/disable; the blues listing covers a 72-endpoint subset focused on the core project, fleet, device, and routing operations.

Is the Blues Notehub API free?

Notehub offers a free developer tier sufficient for prototyping with caps on devices, monthly events, and data egress. Paid tiers scale device count and event volume, billed per the active billing account configured in Notehub.