AsyncAPI channel · ThingSpeak · ThingSpeak MQTT API

`channels/{channelID}/subscribe/fields/field{fieldNumber}/{readAPIKey}`

Name: channels/{channelID}/subscribe/fields/field{fieldNumber}/{readAPIKey}
Creator: ThingSpeak

Subscribe to a specific field on a channel. Requires the channel's Read API Key in the topic.

Open source AsyncAPI → All ThingSpeak channels ThingSpeak provider profile

Provider: ThingSpeak AsyncAPI: v2.6.0 Spec: ThingSpeak MQTT API Operations: 1 Messages: 1

Channel address

channels/{channelID}/subscribe/fields/field{fieldNumber}/{readAPIKey}

Parameters

channelID —
fieldNumber —
readAPIKey —

Operations

subscribeFieldFeed

Messages

FieldValue

Content-Type: text/plain

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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.