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
Resource ID for the requested entity. Example: art_01JXY9AZK4KV
Response
application/json- results[] object array
Items in this page. Revision summary.
+ - Show Child Attributes
- id string
Revision ID.
- version integer
Article version this revision captured.
- title string | null
- source string | null
Write channel of the publish.
- comment string | null
- createdAt string
ISO 8601 timestamp in UTC.
- has_more boolean
Whether more items are available after this page.
- next_cursor string | null
Cursor to pass as
start_cursorfor the next page, or null on the last page.