AsyncAPI channel · Edge Impulse · Edge Impulse Remote Management API

/

A single duplex WebSocket session between one device (or the serial daemon acting as its proxy) and the Edge Impulse remote management service. Devices authenticate by sending their project apiKey inside the Hello message.

Open source AsyncAPI → All Edge Impulse channels Edge Impulse provider profile
Provider: Edge Impulse AsyncAPI: v3.0.0 Spec: Edge Impulse Remote Management API Operations: 7 Messages: 12

Channel address

/

Operations

send
sendHello
Device announces itself and authenticates.
receive
receiveHelloResponse
Server acknowledges the handshake.
receive
receiveSampleRequest
Server requests a new sample.
send
sendSampleResponse
Device accepts or rejects the sampling request.
send
sendSampleProgress
Device reports sampling progress.
receive
receiveSnapshotControl
Server starts or stops snapshot streaming (protocol v3+).
send
sendSnapshotFrame
Device streams a snapshot frame.

Messages

Hello
First message of the session. Only a device sends it; the encoding of this message (JSON or CBOR) fixes the encoding for the rest of the session.
Content-Type: application/json
HelloResponse
Server acknowledgement of the device handshake.
Content-Type: application/json
Sample
Server instructs the device to acquire a new sample.
Content-Type: application/json
SampleResponse
Device acknowledges (or rejects) the sampling request.
Content-Type: application/json
SampleStarted
Sampling has begun on the device.
Content-Type: application/json
SampleProcessing
The device is processing the acquired sample.
Content-Type: application/json
SampleReading
The daemon is pulling data off the device over serial; carries a progress percentage. May be sent repeatedly.
Content-Type: application/json
SampleUploading
The device is uploading the sample to the Ingestion API.
Content-Type: application/json
SampleFinished
The sampling cycle is complete.
Content-Type: application/json
StartSnapshot
Server asks the device to begin streaming snapshot frames. Protocol v3 and above.
Content-Type: application/json
StopSnapshot
Server asks the device to stop streaming snapshot frames. Protocol v3 and above.
Content-Type: application/json
SnapshotFrame
A single snapshot frame from the device.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This channel 
curl "https://apis.io/api/v1/channels/session"
All event channels 
curl "https://apis.io/api/v1/channels?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.