How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Blues device API

Device operations

Blues device API is one of 14 APIs that Blues publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 11 JSON Schema definitions.

Tagged areas include Device. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 11 JSON Schemas.

This API exposes 31 operations across 23 paths, and defines 22 schemas. It is described by OpenAPI 3.0.3, at version 1.2.0.

Requests are made against a single base URL, https://api.notefile.net.

31 operations 23 paths 22 schemas 4 DELETE17 GET7 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.2.0
Base URL
https://api.notefile.net
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Blues device API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (personalAccessToken).

  • personalAccessToken — Use a personal access token from notehub.io/api-access

Paths & Operations 31

Across 23 paths, the API surfaces 31 operations — 4 DELETE, 17 GET, 7 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

device 31

Device operations

GET
/v1/products/{productUID}/devices/{deviceUID}/environment_variables_with_pin
Get environment variables of a device with device pin authorization
GetDeviceEnvironmentVariablesByPin 3 params → 200default
PUT
/v1/products/{productUID}/devices/{deviceUID}/environment_variables_with_pin
Set environment variables of a device with device pin authorization
SetDeviceEnvironmentVariablesByPin 3 params body → 200default
GET
/v1/projects/{projectOrProductUID}/devices
Get Devices of a Project
GetDevices 12 params → 200default
DELETE
/v1/projects/{projectOrProductUID}/devices/{deviceUID}
Delete Device
DeleteDevice 2 params → 204default
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}
Get Device
GetDevice 2 params → 200default
POST
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/disable
Disable Device
DisableDevice 2 params → 200default
POST
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/enable
Enable Device
EnableDevice 2 params → 200default
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/environment_hierarchy
Get environment variable hierarchy for a device
GetDeviceEnvironmentHierarchy 2 params → 200404500
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/environment_variables
Get environment variables of a device
GetDeviceEnvironmentVariables 2 params → 200default
PUT
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/environment_variables
Set environment variables of a device
SetDeviceEnvironmentVariables 2 params body → 200default
DELETE
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/environment_variables/{key}
Delete environment variable of a device
DeleteDeviceEnvironmentVariable 3 params → 200default
DELETE
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/files
Deletes Notefiles and the Notes they contain.
DeleteNotefiles 2 params body → 200default
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/files
Lists .qi and .db files for the device
ListNotefiles 4 params → 200default
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/health-log
Get Device Health Log
GetDeviceHealthLog 5 params → 200default
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/journeys
Get the list of journeys for a device, derived from track.qo events. Returns journey metadata only (no event payloads). Capped at 100 most recent journeys; hasmore is true when the cap is hit.
GetDeviceJourneys 4 params → 200default
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/journeys/{journeyID}
Get a single journey for a device along with its track.qo events. The events array is paginated via pageSize / pageNum; use journey.hasmore to detect additional pages.
GetDeviceJourney 5 params → 200default
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/latest
Get Device Latest Events
GetDeviceLatestEvents 2 params → 200default
POST
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/notefiles/{notefileID}
Creates an empty Notefile on the device.
CreateNotefile 3 params → 200default
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/notes/{notefileID}
For .qi files, returns the queued up notes. For .db files, returns all notes in the notefile
GetNotefile 6 params → 200default
POST
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/notes/{notefileID}
Adds a Note to a Notefile, creating the Notefile if it doesn't yet exist.
AddQiNote 3 params body → 200default
DELETE
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/notes/{notefileID}/{noteID}
Delete a note from a .db or .qi notefile
DeleteNote 4 params → 200default
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/notes/{notefileID}/{noteID}
Get a note from a .db or .qi notefile
GetDbNote 6 params → 200default
POST
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/notes/{notefileID}/{noteID}
Add a Note to a .db notefile. if noteID is '-' then payload is ignored and empty notefile is created
AddDbNote 4 params body → 200default
PUT
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/notes/{notefileID}/{noteID}
Update a note in a .db or .qi notefile
UpdateDbNote 4 params body → 200default
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/plans
Get Data Plans associated with the device, this include the primary sim, any external sim, as well as any satellite connections.
GetDevicePlans 2 params → 200default
POST
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/provision
Provision Device for a Project
ProvisionDevice 2 params body → 200default
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/public-key
Get Device Public Key
GetDevicePublicKey 2 params → 200default
GET
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/sessions
Get Device Sessions
GetDeviceSessions 7 params → 200default
POST
/v1/projects/{projectOrProductUID}/devices/{deviceUID}/signal
Send a signal from Notehub to a Notecard.
SignalDevice 2 params body → 200default
GET
/v1/projects/{projectOrProductUID}/devices/public-keys
Get Device Public Keys of a Project
GetDevicePublicKeys 3 params → 200default
GET
/v1/projects/{projectOrProductUID}/fleets/{fleetUID}/devices
Get Devices of a Fleet within a Project
GetFleetDevices 12 params → 200default

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are Event (60 properties), DeviceSession (57 properties), Device (20 properties), TowerLocation (14 properties). Each schema is shown below with its type and property counts.

Note
object
7 properties 3 required
TowerLocation
object
14 properties
DeviceSession
object
57 properties
DFUEnv
object
2 properties
Error
object
6 properties 3 required
DataUsage
object
3 properties 3 required
Location
object
6 properties 6 required
NoteInput
object
2 properties
Notefile
object
3 properties 2 required
EnvironmentVariables
object
1 property 1 required
DFUState
object
13 properties
DeviceUsage
object
10 properties
CellularPlan
object
8 properties
Body
object
1 property
Event
object
60 properties
EnvTreeJsonNode
object
11 properties 5 required
Contact
object
4 properties
CellularUsage
array
EnvVar
object
4 properties
SimUsage
object
5 properties
NotefileList
array
Array of notefiles, each containing its notes.
Device
object
20 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

blues-wireless-device-api-openapi.yml Raw ↑

Other APIs Blues publishes across the network.

Notecard API
Blues alert API
Blues authorization API
Blues billing_account API
Blues event API
Blues external devices API
Blues jobs API
Blues monitor API
Blues organization API
Blues project API
Blues route API
Blues usage API
Where this information came from

This is an independent, third-party profile of Blues device API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.