AsyncAPI channel · Fitbit · Fitbit Subscriptions Webhooks

`/subscriber`

Single subscriber URL that receives notifications for every collection the application has subscribed to. Fitbit may batch multiple notifications into one POST as a JSON array.

Open source AsyncAPI → All Fitbit channels Fitbit provider profile

Provider: Fitbit AsyncAPI: v2.6.0 Spec: Fitbit Subscriptions Webhooks Operations: 1 Messages: 5

Channel address

/subscriber

Operations

receiveSubscriptionNotification

Receive subscription notification batch

Messages

ActivitiesNotification

New activity data is available for the user.

Content-Type: application/json

BodyNotification

New body (weight, body fat, BMI) data is available for the user.

Content-Type: application/json

FoodsNotification

New food / water log data is available for the user.

Content-Type: application/json

SleepNotification

New sleep log data is available for the user.

Content-Type: application/json

UserRevokedAccessNotification

The user revoked the application's access. The application should stop calling Fitbit APIs and delete any related access/refresh tokens.

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.