Ferndesk

Feedback

Update feedback triage

Marks a feedback entry resolved or unresolved (triage). Requires the content:write scope.

Required scope: content:write

PATCH /feedback/{id}

Update feedback triage

curl --request PATCH \
  --url 'https://api.ferndesk.com/v1/feedback/{ID}' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
  "key": "value"
}'
{
  "id": "<string>",
  "resolved": true
}

Updated

Authorizations

  • Authorization string required header

    All requests require a Bearer token in the Authorization header. API keys are prefixed with fdsk_ 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 translations
    • content:write: Create and edit article drafts, users, tasks; move articles and collections
    • content:publish: Publish, unpublish, restore, and trash content (make changes live)
    • analytics:read: Read help center reporting, analytics, and article feedback
    • conversations:read: Read AI assistant conversations and transcripts
    • webhooks:manage: Create and manage outbound webhook subscriptions

    Granting content:write or content:publish implies content:read. Keys minted before scoping have null scopes = full access (legacy mode).

Path Parameters

  • id string required

Request Body

application/json
  • resolved boolean required

    Mark the feedback resolved or unresolved.

Response

application/json
  • id string
  • resolved boolean