Blues Notehub API

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

★ Only Publicly Available SpecIOTDevice Managementbearer72 EndpointsREST

For Agents

Provision Blues Notecard devices, group them into fleets, push configuration, and route incoming events from cellular IoT hardware to your cloud.

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:
"list Notehub devices in a project"

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

Capabilities

What an agent can do with Blues Notehub API API.

Provision new Notecard devices into a Notehub project and assign them to fleets

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

Configure routes that forward incoming Notes to AWS, Azure, MQTT, or HTTP endpoints

Set up monitors that alert on device dropout, route failure, or threshold breach

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. Notehub is the Blues cloud service for managing cellular IoT devices built around the Notecard module. The API exposes projects, products, fleets, devices, events, routes, monitors, billing accounts, and usage data, letting integrators provision new devices, group them into fleets, push environment variables, and route incoming Notes to downstream cloud services. Authentication uses Bearer tokens obtained from /oauth2/token using a Personal Access Token or OAuth client credentials.

Use Cases

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

★ Fleet provisioning at manufacturing time

Bring a batch of newly manufactured Notecard devices online by registering them in Notehub and assigning them to the right fleet. Use POST /v1/projects/{projectOrProductUID}/fleets to create the fleet, then PUT /v1/projects/{projectOrProductUID}/fleets/{fleetUID} to add devices. Suitable for contract manufacturing handoff, kit-based product launches, and staged rollouts.

Call POST /v1/projects/{projectOrProductUID}/fleets to create a fleet named 'pilot-batch-1', then add the listed device UIDs to it.

Configuration rollout across fleet

Push configuration changes to fielded devices through environment variables, which the Notecard surfaces to host firmware. PUT /v1/projects/{projectOrProductUID}/environment_variables sets project-wide values, while the fleet-scoped variant targets a single fleet. Useful for rolling out telemetry interval changes, feature flags, or backend URL updates without a firmware push.

Call PUT /v1/projects/{projectOrProductUID}/fleets/{fleetUID}/environment_variables with {telemetry_interval: 300} to set a 5-minute interval for all devices in the fleet.

Cloud event routing

Forward incoming Notecard events to a downstream cloud target by creating a Notehub route. Routes can target AWS IoT, Azure IoT Hub, Google Cloud, generic HTTP webhooks, or MQTT brokers, with JSONata transforms applied before delivery. Manage routes via /v1/projects/{projectOrProductUID}/routes and inspect their delivery health.

List existing routes via GET /v1/projects/{projectOrProductUID}/routes and return each route's name, target type, and last successful delivery timestamp.

Device health monitoring

Detect device dropout and route failures by configuring Notehub monitors. Monitors evaluate conditions on incoming events and trigger notifications when thresholds are breached. Combine with /v1/projects/{projectOrProductUID}/devices/{deviceUID}/events to investigate per-device history when a monitor fires.

Pull GET /v1/projects/{projectOrProductUID}/devices and identify any device whose last event timestamp is older than 24 hours.

AI agent IoT operations assistant

Let an AI agent answer operations questions and run runbooks against a Blues fleet. 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 fleet ops chatbots, on-call investigation copilots, and customer support agents who need read access to device state.

Search Jentic for 'list Notehub devices in a project', load the schema, and execute it with the projectOrProductUID to return all devices and their last-seen timestamps.

Key Endpoints

72 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

List all accessible projects

POST

/v1/projects/{projectOrProductUID}/fleets

Create a new fleet within a project

GET

/v1/projects/{projectOrProductUID}/devices

List devices in a project

PUT

/v1/projects/{projectOrProductUID}/environment_variables

Set project-wide environment variables

POST

/v1/projects/{projectOrProductUID}/clone

Clone a project as a template

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

List all accessible projects

POST

/v1/projects/{projectOrProductUID}/fleets

Create a new fleet within a project

GET

/v1/projects/{projectOrProductUID}/devices

List devices in a project

PUT

/v1/projects/{projectOrProductUID}/environment_variables

Set project-wide 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 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. 'list Notehub devices' or 'create a Notehub route') and Jentic returns the matching operation across the 72 endpoints with its input schema, so the agent can call the right path without browsing dev.blues.io.

Time to first call

Direct integration: 1-2 days for OAuth token exchange, project/fleet/device hierarchy mapping, and route configuration. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Blues Notehub API

Sister Notehub spec under blues.io with expanded endpoint coverage including firmware and notes

Choose blues.io when the agent needs firmware update, notes, or broader endpoint coverage; this entry covers the core 72-endpoint surface

Alternative

Blynk

IoT platform with device dashboards and mobile app — alternative for hobbyist and prosumer IoT instead of cellular Notecard

Choose Blynk when the user is on Wi-Fi or BLE devices and needs a mobile dashboard; choose Blues for cellular Notecard fleets

Complementary

Blueshift

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

Use when an agent must trigger a Blueshift campaign in response to a Notehub event such as device offline

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. You exchange a Personal Access Token (issued from the Notehub dashboard) for a short-lived OAuth bearer token via POST /oauth2/token, then pass it as Authorization: Bearer <token>. Through Jentic, the PAT is stored encrypted and the token exchange happens automatically at execution.

Can I provision new Notecard devices through this API?

Yes. Devices typically activate themselves on first connection, but you can pre-provision and assign them via the project and fleet endpoints. Use GET /v1/projects/{projectOrProductUID}/devices to enumerate, and PUT /v1/projects/{projectOrProductUID}/fleets/{fleetUID} to attach a device UID to a fleet.

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 below 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 push configuration to a fleet through Jentic?

Search Jentic for 'set Notehub environment variables for a fleet', load the schema for PUT /v1/projects/{projectOrProductUID}/fleets/{fleetUID}/environment_variables, and execute it with the variable map. Install with pip install jentic and call await client.execute(ExecutionRequest(...)).

Does Notehub support routing events to AWS or Azure?

Yes. The /v1/projects/{projectOrProductUID}/routes endpoints let you create routes targeting AWS IoT, Azure IoT Hub, Google Cloud, generic HTTP, or MQTT brokers. Routes support JSONata transforms so events can be reshaped before delivery.

Is the Blues Notehub API free?

Notehub offers a free developer tier sufficient for prototyping (with limits on devices, events per month, and data egress). Paid tiers scale device count and event volume, billed per the active billing account.