> ## Documentation Index > Fetch the complete documentation index at: https://docs.useboom.ai/llms.txt > Use this file to discover all available pages before exploring further. # List email templates > Everything a SEND_EMAIL node needs: the PUBLISHED email templates it can use, the org's email readiness, and the senders available as From / Reply-To overrides. Email has no channelId — it sends from the org's verified domain — which is why it is not in journeys_message_channels. Publish refuses a SEND_EMAIL node unless readiness.verified and readiness.hasSender are both true (or the node sets a fromSenderIdOverride whose sender is usableAsFrom). ## OpenAPI ````yaml /api-reference/openapi.json get /api/v1/journeys/email-templates openapi: 3.1.0 info: title: Boom API version: 1.0.0 description: >- Boom's public REST API — one uniform surface over every platform capability. CDP: upsert people and custom objects, define object and relationship types, link and unlink relationships, and record behavioral events — one record per request or up to 1000 per request via the `/batch` endpoints. Segments: read (list, read, membership) and full authoring — discover the filterable catalog, validate a filter, create and update segments, preview match counts, and trigger evaluation. Initiatives: create and configure outreach initiatives, link WhatsApp templates, drive the lifecycle (launch, cancel, archive), and read collected-data summaries. Participants: enroll people into an active initiative, track their status, read conversation transcripts, and stop outreach. Journeys: read-only access to always-on message flows and their metrics. WhatsApp templates: list your WhatsApp numbers and list, read, and create message templates. The same capabilities are exposed as MCP tools with identical schemas. servers: - url: https://www.useboom.ai description: Production - url: https://dev.useboom.ai description: Development (sandbox — use a development organization API key) security: - bearerAuth: [] paths: /api/v1/journeys/email-templates: get: tags: - Journeys summary: List email templates description: >- Everything a SEND_EMAIL node needs: the PUBLISHED email templates it can use, the org's email readiness, and the senders available as From / Reply-To overrides. Email has no channelId — it sends from the org's verified domain — which is why it is not in journeys_message_channels. Publish refuses a SEND_EMAIL node unless readiness.verified and readiness.hasSender are both true (or the node sets a fromSenderIdOverride whose sender is usableAsFrom). operationId: journeys_email_templates responses: '200': description: Success content: application/json: schema: $schema: https://json-schema.org/draft/2020-12/schema type: object properties: readiness: type: object properties: configured: type: boolean description: An email domain has been added for this org. verified: type: boolean description: That domain passed DNS verification. domain: anyOf: - type: string - type: 'null' hasSender: type: boolean description: >- A default From resolves: a default sender on the verified domain, or the legacy domain fromAddress. required: - configured - verified - domain - hasSender additionalProperties: false senders: type: array items: type: object properties: id: type: string displayName: type: string address: type: string isDefault: type: boolean usableAsFrom: type: boolean description: >- On the verified domain, so valid as fromSenderIdOverride. An off-domain sender is Reply-To only. required: - id - displayName - address - isDefault - usableAsFrom additionalProperties: false data: type: array items: type: object properties: id: type: string description: Use as the node's templateId. name: type: string subject: type: string variables: type: array items: type: object properties: key: type: string path: type: string required: - key - path additionalProperties: false description: >- Placeholders the template uses. `key` is what a node's `bindings` map from; `path` is what it resolves to when left unbound. fromSenderId: anyOf: - type: string - type: 'null' replyToSenderId: anyOf: - type: string - type: 'null' required: - id - name - subject - variables - fromSenderId - replyToSenderId additionalProperties: false required: - readiness - senders - data additionalProperties: false '400': description: Validation failed or the request cannot proceed. content: application/json: schema: type: object properties: error: type: object properties: code: type: string description: Stable machine-readable error code (snake_case). message: type: string required: - code - message required: - error '401': description: Missing, malformed, or revoked API key. content: application/json: schema: type: object properties: error: type: object properties: code: type: string description: Stable machine-readable error code (snake_case). message: type: string required: - code - message required: - error '404': description: The resource does not exist in this organization. content: application/json: schema: type: object properties: error: type: object properties: code: type: string description: Stable machine-readable error code (snake_case). message: type: string required: - code - message required: - error '409': description: >- Conflicts with the current state (duplicates, wrong lifecycle state). content: application/json: schema: type: object properties: error: type: object properties: code: type: string description: Stable machine-readable error code (snake_case). message: type: string required: - code - message required: - error '422': description: The request is well-formed but semantically invalid. content: application/json: schema: type: object properties: error: type: object properties: code: type: string description: Stable machine-readable error code (snake_case). message: type: string required: - code - message required: - error '429': description: Rate limit exceeded — retry after `Retry-After`. content: application/json: schema: type: object properties: error: type: object properties: code: type: string description: Stable machine-readable error code (snake_case). message: type: string required: - code - message required: - error '500': description: Internal server error. content: application/json: schema: type: object properties: error: type: object properties: code: type: string description: Stable machine-readable error code (snake_case). message: type: string required: - code - message required: - error '503': description: Transient error — retry with a narrower request. content: application/json: schema: type: object properties: error: type: object properties: code: type: string description: Stable machine-readable error code (snake_case). message: type: string required: - code - message required: - error components: securitySchemes: bearerAuth: type: http scheme: bearer description: 'Organization API key, sent as `Authorization: Bearer boom_org_...`.' ````