When to use snippets Common acknowledgements, policy explanations, troubleshooting steps, or closing messages that you send across many tickets. Standardize how your team communicates so every requester gets the same brand voice and approved wording. Drop a known-good response in seconds instead of composing it from scratch each time. *** Manage snippets via the API Each snippet is scoped to a single workspace and has two required fields: * **`name`** — A short label used to find the snippet (for example, `Password reset acknowledged`). * **`content`** — The reply text inserted into a ticket message. The API also returns `id`, `workspaceId`, `authorId`, `createdAt`, and `updatedAt`. All snippet endpoints require an API key with workspace access. See the [API overview](/api/overview) for authentication details. Create a snippet ```bash theme={"system"} curl --request POST \ --url https://core.ravenna.ai/api/snippets \ --header 'x-ravenna-api-token: ' \ --header 'content-type: application/json' \ --data '{ "name": "Password reset acknowledged", "content": "Thanks for reaching out — we've received your password reset request and will follow up shortly." }' ``` List snippets ```bash theme={"system"} curl --request GET \ --url https://core.ravenna.ai/api/snippets \ --header 'x-ravenna-api-token: ' ``` Update a snippet ```bash theme={"system"} curl --request PUT \ --url https://core.ravenna.ai/api/snippets/{id} \ --header 'x-ravenna-api-token: ' \ --header 'content-type: application/json' \ --data '{ "name": "Password reset acknowledged", "content": "Thanks for reaching out — our IT team has your password reset request and will respond within one business hour." }' ``` Delete a snippet ```bash theme={"system"} curl --request DELETE \ --url https://core.ravenna.ai/api/snippets/{id} \ --header 'x-ravenna-api-token: ' ``` See the full endpoint reference under [API → Snippets](/api/overview).