> ## Documentation Index > Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt > Use this file to discover all available pages before exploring further. # List Workspace WhatsApp Templates > Returns the workspace's stored WhatsApp templates, including Content SIDs, approval status, body, and variable keys. ## OpenAPI ````yaml GET /v1/workspaces/{id}/whatsapp-templates openapi: 3.0.0 info: title: Conduit API version: 1.0.0 description: Public API for Conduit. servers: - url: https://api.conduit.ai description: Production security: [] tags: - name: meta description: Discovery and API metadata endpoints. - name: agents description: >- V2 chat agent configuration, including instructions, skills, triggers, and automation behavior. - name: contacts description: >- Contact profile and contact-scoped related resources such as tickets and calls. - name: workspaces description: Workspaces accessible to the current API token. - name: escalations description: >- Chat escalations that require operator review, including message, proposed response, and disposition context when available. - name: conversations description: >- Canonical message threads. Use these endpoints to list threads, inspect conversation state, read transcripts, and send replies. - name: tickets description: >- Operational queue items tied to conversations, including ticket-scoped transcripts and replies. - name: calls description: Phone call records, transcripts, summaries, and recordings when available. - name: reservations description: >- PMS reservations synced from the workspace's integrations (Hostaway, Guesty, Airbnb, etc.), including guest identity, payment status, and stay dates. - name: appointments description: >- Scheduled appointments (bookings) backed by the Conduit booking service. Exposes allocation context and the upstream booking-service `external_id`. - name: helpdesk_tickets description: >- Helpdesk tickets mirrored from external helpdesk integrations (Zendesk, Pylon, Plain), including requester identity and upstream metadata. - name: kb description: >- Knowledge base search and node management. Nodes represent knowledge base entries (files or directories), chunks are the indexed retrieval units used by search. - name: skills description: >- Workspace agent skills that can be attached to V2 chat agents. Sidebar/global-assistant skills are intentionally excluded. paths: /v1/workspaces/{id}/whatsapp-templates: get: tags: - workspaces summary: List WhatsApp templates description: >- Returns the workspace's stored WhatsApp templates, including Twilio Content SIDs, approval status, template body, and variable keys. Use approved `content_sid` values with proactive WhatsApp contact message requests. operationId: listWorkspaceWhatsappTemplates parameters: - schema: type: string example: j57demo8f8x7c9v0n2q4r6t8y1u3i5o description: Workspace identifier. required: true description: Workspace identifier. name: id in: path responses: '200': description: Workspace WhatsApp templates content: application/json: schema: type: object properties: data: type: array items: type: object properties: id: type: string workspace_id: type: string content_sid: type: string friendly_name: type: string language: type: string status: type: string category: type: string content_type: type: string rejection_reason: type: string body: type: string variables: type: object additionalProperties: {} created_at: type: string updated_at: type: string required: - id - workspace_id - content_sid - friendly_name - language - status - category - content_type - rejection_reason - body - variables - created_at - updated_at required: - data description: >- WhatsApp templates stored for the workspace. Use `content_sid` and `variables` with proactive WhatsApp contact sends. example: data: - id: HXaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa workspace_id: j57demo8f8x7c9v0n2q4r6t8y1u3i5o content_sid: HXaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa friendly_name: arrival_reminder language: en status: approved category: UTILITY content_type: twilio/text rejection_reason: '' body: Hi {{1}}, your check-in is {{2}}. variables: '1': Guest name '2': Check-in time created_at: '2026-04-03T03:15:02.000Z' updated_at: '2026-04-03T03:15:04.000Z' '400': description: Invalid request content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '401': description: Unauthorized content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '403': description: Forbidden content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '404': description: Not found content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '429': description: Rate limit exceeded content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API Token description: >- Conduit API token. Use `Authorization: Bearer `. Read/write endpoints require a token with write access. ````