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).
Query Parameters
- page_size integer
Number of items to return per page (1-100). Example: 20
- start_cursor string
Opaque pagination cursor. Pass the
next_cursorfrom a previous response to fetch the next page. Example: eyJ2IjoxLCJrIjpbIjIwMjYtMDEtMDEiLCJhcnRfMSJdfQ - status string
Filter by task status. Example: completed
Response
application/json- results[] object array
Items in this page. Task payload.
+ - Show Child Attributes
- id string
Task ID (
tsk_...). - title string | null
Task title. If omitted on create, Fern generates one after task creation.
- status string
Task processing status.
- 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.