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 external devices API

APIs for events and sessions for external devices

Blues external devices 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 external devices. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 11 JSON Schemas.

This API exposes 3 operations across 3 paths, and defines 5 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.

3 operations 3 paths 5 schemas 3 POST

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 external devices 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 3

Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.

external devices 3

APIs for events and sessions for external devices

POST
/v1/products/{productUID}/ext-devices/{deviceUID}/event
Creates an event using specified webhook
CreateEventExtDevice 2 params body → 200default
POST
/v1/products/{productUID}/ext-devices/{deviceUID}/session/close
Closes the session for the specified device if open
ExtDeviceSessionClose 2 params body → 200default
POST
/v1/products/{productUID}/ext-devices/{deviceUID}/session/open
Create a Session for the specified device. | If a session is currently open it will be closed and a new one opened.
ExtDeviceSessionOpen 2 params body → 200default

Schemas 5

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

TowerLocation
object
14 properties
Event
object
60 properties
DeviceSession
object
57 properties
DeviceUsage
object
10 properties
Error
object
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

blues-wireless-external-devices-api-openapi.yml Raw ↑

Other APIs Blues publishes across the network.

Notecard API
Blues alert API
Blues authorization API
Blues billing_account API
Blues device API
Blues event 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 external devices 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.