Authorizations
- Authorization string required header
All requests require a Bearer token in the
Authorizationheader. API keys are prefixed withfdsk_and should be kept secret. You can generate and manage keys from the Developer settings page.Keys can be restricted to any subset of these scopes (each endpoint lists the scope it requires via
x-required-scopes):content:read: Read and search help center articles, collections, sections, and translationscontent:write: Create and edit article drafts, users, tasks; move articles and collectionscontent:publish: Publish, unpublish, restore, and trash content (make changes live)analytics:read: Read help center reporting, analytics, and article feedbackconversations:read: Read AI assistant conversations and transcriptswebhooks:manage: Create and manage outbound webhook subscriptions
Granting
content:writeorcontent:publishimpliescontent:read. Keys minted before scoping have null scopes = full access (legacy mode).
Path Parameters
- deliveryId string required
Delivery ID (
whdl_...). Example: whdl_01JXY9AZK4KV - id string required
Webhook endpoint ID (
whep_...). Example: whep_01JXY9AZK4KV
Response
application/json- id string
Delivery ID (
whdl_...). - eventType string
Event type delivered.
- status string enum enum
Delivery lifecycle status. Allowed values: pending, success, failed.
- responseStatus integer | null
HTTP status returned by the endpoint, or null before the first attempt / on a network error.
- attempts integer
Delivery attempts made so far.
- error string | null
Last error message, if the most recent attempt failed.
- createdAt string
ISO 8601 timestamp in UTC.
- deliveredAt string | null
When the delivery first succeeded, if it has.
- nextRetryAt string | null
When the next retry is scheduled, for pending failed deliveries.