AsyncAPI channel · Fitbit · Fitbit Subscriptions Webhooks

/subscriber/verify

Subscriber verification handshake. When a subscriber URL is registered or updated on dev.fitbit.com, Fitbit issues two GET requests with a `verify` query parameter. Respond 204 to the verification code shown in the developer console and 404 to the intentionally-incorrect second code.

Open source AsyncAPI → All Fitbit channels Fitbit provider profile
Provider: Fitbit AsyncAPI: v2.6.0 Spec: Fitbit Subscriptions Webhooks Operations: 1 Messages: 1

Channel address

/subscriber/verify

Operations

receiveSubscriberVerification
Subscriber verification handshake

Messages

SubscriberVerification
Subscriber registration handshake. Two GETs are issued — one with the correct verification code (respond 204) and one with an incorrect code (respond 404). Responses must arrive within 5 seconds.
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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.