Templates API
This article and the rest of the API documentation in this section are written for a technical audience — integrators and developers connecting external systems to Tickiti. Familiarity with HTTP, REST, JSON and bearer-token authentication is assumed.
The Templates API manages email/notification templates and FAQs (both stored as templates, distinguished by type). Every endpoint runs as the token’s owner and is gated by the templates ability plus the owner’s admin role. Stock responses are managed through the Settings API.
Abilities and conventions
templates:read— read endpoints.templates:write— create / update / delete. Write implies read.
All endpoints are POST and JSON. Create/update accept a type of template or faq; inline base64 images in content are extracted automatically, exactly as in the UI.
Endpoints
| Method & path | Ability | Purpose |
|---|---|---|
| POST /api/v1/templates | templates:read | List templates (excludes FAQs and stock responses) |
| POST /api/v1/templates/faqs | templates:read | List FAQs |
| POST /api/v1/templates/show | templates:read | Fetch one template by template_id |
| POST /api/v1/templates/search | templates:read | Search templates (search, mode, type) |
| POST /api/v1/templates/create | templates:write | Create a template or FAQ (type) |
| POST /api/v1/templates/update | templates:write | Update a template/FAQ (template object) |
| POST /api/v1/templates/delete | templates:write | Delete a template by template_id |