Ferndesk

Articles

Restore a trashed article

Restores a trashed article back to the status it had before trashing. Requires the content:write scope; if the article was PUBLISHED when trashed, restoring brings live content back online and additionally requires content:publish.

Required scope: content:write

POST /articles/{id}/restore

Restore a trashed article

curl --request POST \
  --url 'https://api.ferndesk.com/v1/articles/{ID}/restore' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN'
{
  "id": "<string>",
  "status": "<string>"
}

Restored

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

    Resource ID for the requested entity. Example: art_01JXY9AZK4KV

Response

application/json
  • id string

    Ferndesk article ID (art_...).

  • status string

    Status after restore.