> ## Documentation Index > Fetch the complete documentation index at: https://docs.go.aiinsurance.io/llms.txt > Use this file to discover all available pages before exploring further. # List Policy Sendable Email Templates > Lists the email templates the caller can send from this record: the latest version of each template of the record's type. Without `fromPacket`, only templates that need no packet; with `fromPacket=true`, every template, for sending from one of the record's packets. These are the templates the app's Send email dialog offers. Answers `404` while email is not turned on for the company. The policy's twin of the record route under `/entities`: policies live under the policy API. **Required permission:** `email.send` and `policy.view`. ## OpenAPI ````yaml /openapi/generated-external-api.yaml get /api/v1/companies/{companyId}/policies/{policyId}/sendable-email-templates openapi: 3.0.3 info: title: AI Insurance External API description: External API for AI Insurance platform version: 1.0.0 contact: email: support@aiinsurance.io servers: - url: https://go.aiinsurance.io description: Production security: - ApiKeyAuth: [] paths: /api/v1/companies/{companyId}/policies/{policyId}/sendable-email-templates: get: tags: - Record Emails summary: List Policy Sendable Email Templates description: > Lists the email templates the caller can send from this record: the latest version of each template of the record's type. Without `fromPacket`, only templates that need no packet; with `fromPacket=true`, every template, for sending from one of the record's packets. These are the templates the app's Send email dialog offers. Answers `404` while email is not turned on for the company. The policy's twin of the record route under `/entities`: policies live under the policy API. **Required permission:** `email.send` and `policy.view`. operationId: listPolicySendableEmailTemplates parameters: - $ref: '#/components/parameters/companyId' - $ref: '#/components/parameters/policyIdPath' - $ref: '#/components/parameters/emailFromPacket' responses: '200': description: The templates, by name content: application/json: schema: type: object required: - items properties: items: type: array items: $ref: '#/components/schemas/SendableEmailTemplate' examples: fromPacket: summary: From a packet value: items: - id: 550e8400-e29b-41d4-a716-446655440401 name: Quote ready version: 2 requiresPacket: false attachPacketDefault: false - id: 550e8400-e29b-41d4-a716-446655440402 name: Quote packet version: 1 requiresPacket: true attachPacketDefault: true '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: The record does not exist, or email is not turned on for the company content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: recordNotFound: summary: Record not found value: error: code: NotFoundError message: Quote 550e8400-e29b-41d4-a716-446655440301 not found userMessages: - Quote 550e8400-e29b-41d4-a716-446655440301 not found '500': $ref: '#/components/responses/InternalServerError' security: - BearerAuth: [] - ApiKeyAuth: [] components: parameters: companyId: name: companyId in: path required: true schema: type: string format: uuid description: Company identifier policyIdPath: name: policyId in: path required: true schema: type: string format: uuid description: Policy identifier emailFromPacket: name: fromPacket in: query required: false schema: type: boolean default: false description: >- `true` lists the templates for sending from one of the record's packets, including those that require a packet. Otherwise only templates that need no packet are listed. schemas: SendableEmailTemplate: type: object description: The latest version of an email template the record can send. required: - id - name - version - requiresPacket - attachPacketDefault properties: id: type: string format: uuid description: The template version's id. Send it as `templateId`. name: type: string version: type: integer requiresPacket: type: boolean description: The template is sent only from a packet, with `packetId`. attachPacketDefault: type: boolean description: >- The app attaches the packet's PDF by default when sending this template. ErrorResponse: type: object description: Standard error response for all external API endpoints required: - error properties: error: type: object required: - code - message properties: code: type: string description: Machine-readable error code example: VALIDATION_ERROR message: type: string description: Human-readable error message example: 'submissionId: Required field is missing' userMessages: type: array description: >- Clean, verbatim-displayable messages — one entry per failure, free of error-code tags, field paths, and internal noise. Suitable for showing to end users as-is. items: type: string example: - Exposures of type 'company' require an address details: type: array description: Additional details for validation errors (field-level errors) items: type: object properties: field: type: string description: The field that caused the error example: submissionId code: type: string description: Stable problem code for this individual validation failure example: BLANK_LIST_ELEMENT reason: type: string description: Stable reason the value violates its canonical contract example: blank-list-element expected: type: string description: The expected canonical value contract example: nonblank trimmed string message: type: string description: Description of the field error example: Required field is missing responses: Unauthorized: description: Unauthorized - Invalid or missing API key content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: missingApiKey: summary: Missing API key value: error: code: AuthenticationError message: API key authentication required userMessages: - API key authentication required invalidApiKey: summary: >- Invalid API key (e.g. unknown key, or a Bearer token used instead of an API key) value: error: code: AuthenticationError message: Invalid API key userMessages: - Invalid API key Forbidden: description: Forbidden - Insufficient permissions content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: insufficientPermissions: summary: Insufficient permissions value: error: code: AuthorizationError message: User is not authorized to perform the requested action userMessages: - User is not authorized to perform the requested action companyMismatch: summary: A valid API key naming another company in the URL value: error: code: AuthorizationError message: API key is not scoped to the requested company userMessages: - API key is not scoped to the requested company InternalServerError: description: Internal Server Error - Unexpected error occurred content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: internalError: summary: Unexpected server error value: error: code: UncaughtActionError message: Uncaught error occurred in userMessages: - An unexpected error occurred. Please try again later. securitySchemes: ApiKeyAuth: type: apiKey in: header name: Authorization description: >- API key authentication. Send your raw API key as the `Authorization` header value with NO scheme prefix — `Authorization: YOUR-API-KEY`. Do NOT prefix it with `Bearer ` or `ApiKey `, and do not use an `X-API-Key` header; those are not accepted. BearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- User-principal OAuth 2.0 Bearer authentication. Send a user-scoped Auth0 access token (audience = the app API audience) as `Authorization: Bearer `. The request resolves to the user's identity and is authorized by their Role on the `{companyId}` in the path — the same role-based permissions the web app enforces. This is the path the MCP connector uses to act on a user's behalf; endpoints that accept it list both `BearerAuth` and `ApiKeyAuth`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.