Skip to main content

[Early Access] Wearable webhook subscription verification

GET /v1/wearables/{provider}/webhook
devhttps://api.sandbox.ovok.com

Early Access — interfaces may change without notice.

Verification handshake endpoint. Some providers (notably Strava) prove they own the callback URL by GETting it with a hub.challenge parameter and a hub.verify_token we agreed on at subscription time. We echo the challenge back if the verify token matches the platform-wide WEARABLES_WEBHOOK_VERIFY_TOKEN environment variable.

You will hit this endpoint only when first registering a webhook subscription with the provider (e.g. via Strava's POST /api/v3/push_subscriptions). After that, the provider POSTs events to the same path — see [Wearable webhook ingress] below.

Example response

{ "hub.challenge": "<echoed verbatim>" }

Returns 400 when the token does not match.

Parameters

NameInTypeRequiredDescription
providerpathstringyesWearable provider slug. Verification handshake is currently used by strava.
hub.verify_tokenqueryyesVerify token agreed with the provider at subscription time. Must equal WEARABLES_WEBHOOK_VERIFY_TOKEN.
hub.challengequeryyesProvider-supplied challenge string. Echoed back verbatim on a successful match.

Responses

CodeDescription
200Success.
400The request could not be operated by the server.
401The resource owner or authorization server denied the request.
404The requested resource could not be found.
422The request could not be validated by the server.
500The server encountered an unexpected condition. Please try again later.

200OkResponseDto (application/json)

Side-effect-only acknowledgement. Body is the literal { "ok": true }.

  • ok: boolean (required)