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
- id string required
Ferndesk article ID (
art_...). Example: art_01JXY9AZK4KV - revisionId string required
Revision ID. Example: rev_01JXY9AZK4KV
Query Parameters
- against string required
Version number or revision ID to diff this revision against. Example: 3
Response
application/json- articleId string
Ferndesk article ID (
art_...). - from object
+ - Show Child Attributes
- revisionId string
- version integer
- to object
+ - Show Child Attributes
- revisionId string
- version integer
- changed boolean
- diff string
Unified-style Markdown line diff.
- addedLines integer
- removedLines integer
- truncated boolean