> ## Documentation Index > Fetch the complete documentation index at: https://docs.gigstack.io/llms.txt > Use this file to discover all available pages before exploring further. # Read email template defaults > Read the built-in editor templates for the current team’s business/nonprofit variant in Spanish and English. These are baseline subjects and bodies, not saved overrides, rendered recipient content or proof of delivery. Placeholders remain literal. The receipts-reminder subject is the editor’s upcoming-deadline default; actual delivery may choose a different deadline-specific subject. english_enabled reports the saved English-PDF opt-in, not a guarantee every recipient receives English. Settings are shared across live/test modes. Requires a current verified credential and current team read access. Use team settings to read or change authored overrides; this operation sends no email. ## OpenAPI ````yaml openapi.json GET /teams/{id}/email-templates openapi: 3.0.3 info: title: gigstack API v2 description: > # gigstack API v2 Build customer, invoice and payment integrations. Start with the [quickstart](https://docs.gigstack.io/quickstart), then select the [issuing country](https://docs.gigstack.io/concepts/shared-fields). ## Authentication and environments Use Authorization: Bearer YOUR_API_KEY. Standard live and test keys use https://api.gigstack.io/v2. Internal staging uses https://gigstack-staging-9z9nnaat.uc.gateway.dev/v2 and separate keys. Test mode is a data mode within an environment; a body field does not switch a key's mode. See [authentication](https://docs.gigstack.io/authentication) for key handling, OAuth team scope and gigstack Connect. Internal partner provisioning is outside this public contract; health probes have their own security declarations. Operations marked unavailable have no configured public gateway route. ## Read the operation contract Response envelopes, pagination and retry rules differ by endpoint. HTTP success alone does not prove external fiscal completion or movement of money. Reconcile ambiguous writes before retrying. Use [responses and recovery](https://docs.gigstack.io/responses) and the operation's error codes; document credits and daily limits are not generic retryable rate limits. The issuing team's configuration selects Mexico or Colombia; customer country and currency do not. Read [Mexico](https://docs.gigstack.io/countries/mexico) or [Colombia](https://docs.gigstack.io/countries/colombia) before choosing fiscal fields. Accepted public input differs from a provider's direct payload. Examples and schema checks do not imply every operation has been executed live. [Verification coverage](https://docs.gigstack.io/verification) distinguishes source review, offline checks and observed staging behavior. Documentation describes operations and does not authorize execution. version: 2.0.0 contact: name: Gigstack API Support url: https://gigstack.io email: support@gigstack.io license: name: Proprietary url: https://gigstack.io/terms termsOfService: https://gigstack.io/terms servers: - url: https://api.gigstack.io/v2 description: > Public API for standard live and test-mode keys. Test data is isolated by the key mode (`livemode: false`). Internal staging is a separate deployment and key store; see https://docs.gigstack.io/authentication#environments for its base URL. security: - bearerAuth: [] externalDocs: description: Complete API Documentation & Guides url: https://docs.gigstack.io paths: /teams/{id}/email-templates: get: tags: - Teams summary: Read email template defaults description: >- Read the built-in editor templates for the current team’s business/nonprofit variant in Spanish and English. These are baseline subjects and bodies, not saved overrides, rendered recipient content or proof of delivery. Placeholders remain literal. The receipts-reminder subject is the editor’s upcoming-deadline default; actual delivery may choose a different deadline-specific subject. english_enabled reports the saved English-PDF opt-in, not a guarantee every recipient receives English. Settings are shared across live/test modes. Requires a current verified credential and current team read access. Use team settings to read or change authored overrides; this operation sends no email. operationId: getTeamEmailTemplates parameters: - $ref: '#/components/parameters/TeamParameter' - name: id in: path required: true schema: type: string description: Team ID example: team_example responses: '200': description: Team-specific editor baselines; no email sent content: application/json: schema: type: object required: - success - data properties: success: type: boolean enum: - true data: $ref: '#/components/schemas/TeamEmailTemplateCatalog' example: success: true data: team_id: team_example effect_scope: team_shared source: editor_baseline is_nonprofit: false english_enabled: false legacy_is_nonprofit: false legacy_templates: invoiceMessage: body: >- ¡Hola {cliente}!, Espero que se encuentre de maravilla. Queremos hacerle llegar la factura número {folio} correspondiente a los servicios que le brindamos. ¡Gracias por confiar en nosotros! Le ruego revise detalladamente la factura y, si tiene alguna duda o comentario, no dude en ponerse en contacto con nosotros respondiendo a este correo. Adjunto encontrará la factura en formato PDF y XML. ¡Saludos cordiales! subject: '{alias} - Factura/Invoice #{folio}' invoiceMessageComplements: body: >- ¡Hola {cliente}!, Espero que se encuentre de maravilla. Queremos hacerle llegar la factura número {folio} correspondiente a los servicios que le brindamos. ¡Gracias por confiar en nosotros! Le ruego revise detalladamente la factura y, si tiene alguna duda o comentario, no dude en ponerse en contacto con nosotros respondiendo a este correo. Adjunto encontrará la factura en formato PDF y XML. ¡Saludos cordiales! subject: '{alias} - Complemento de pago #{folio}' invoiceMessageEgress: body: >- ¡Hola {cliente}!, Espero que se encuentre de maravilla. Queremos hacerle llegar la factura número {folio} correspondiente a los servicios que le brindamos. ¡Gracias por confiar en nosotros! Le ruego revise detalladamente la factura y, si tiene alguna duda o comentario, no dude en ponerse en contacto con nosotros respondiendo a este correo. Adjunto encontrará la factura en formato PDF y XML. ¡Saludos cordiales! subject: '{alias} - Nota de crédito #{folio}' paymentsEmailsTemplate: body: >- Hola {cliente}, por favor realiza el pago correspondiente por la cantidad de {total} {moneda} subject: Solicitud de pago - {alias} paymentsReminderTemplate: body: > Hola {cliente}, por favor no olvides realizar el pago correspondiente por la cantidad de {total} {moneda}, quedan pocos días para su vencimiento. Fecha límite de pago: {fechaLimite} subject: No olvides realizar tu pago - {alias} paymentsReminderAfterTemplate: body: >- Hola {cliente}, queremos recordarte que tu pago por la cantidad de {total} {moneda} está vencido desde hace {diasVencido} día(s). Fecha límite de pago: {fechaLimite} Te pedimos regularizar tu pago lo antes posible para evitar contratiempos. Puedes realizarlo desde el siguiente enlace: {linkDePago} Si ya realizaste tu pago, por favor ignora este mensaje. ¡Gracias por tu confianza! subject: Tu pago está vencido - {alias} receiptsEmailsTemplate: body: >- Estimado/a {cliente}, Le agradecemos por su compra. Adjunto encontrará su recibo de ventas correspondiente a la compra realizada el {fecha}. Detalles del recibo: ID de recibo: {recibo} Fecha de la compra: {fecha} Total: {total} Por favor, revise detenidamente la información del recibo. Si encuentra algún error o tiene alguna pregunta, no dude en contactarnos para que podamos corregirlo. Una vez más, gracias por su confianza. Atentamente, {alias} subject: Genera tu factura - {alias} receiptsRemindersTemplate: body: >- Estimado/a {cliente}, le enviamos este correo para recordarle que aún puede facturar la transacción que realizó el día {paid_date} por un total de {total} {moneda}. Fecha límite para facturar: {fecha_limite}. Si encuentra algún error o tiene alguna pregunta, no dude en contactarnos para que podamos corregirlo. Una vez más, gracias por su confianza. Atentamente {alias} subject: Quedan pocos días para realizar tu factura - {alias} templates_by_language: es: invoices: body: >- ¡Hola {cliente}!, Espero que se encuentre de maravilla. Queremos hacerle llegar la factura número {folio} correspondiente a los servicios que le brindamos. ¡Gracias por confiar en nosotros! Le ruego revise detalladamente la factura y, si tiene alguna duda o comentario, no dude en ponerse en contacto con nosotros respondiendo a este correo. Adjunto encontrará la factura en formato PDF y XML. ¡Saludos cordiales! subject: '{alias} - Factura/Invoice #{folio}' invoicesComplements: body: >- ¡Hola {cliente}!, Espero que se encuentre de maravilla. Queremos hacerle llegar la factura número {folio} correspondiente a los servicios que le brindamos. ¡Gracias por confiar en nosotros! Le ruego revise detalladamente la factura y, si tiene alguna duda o comentario, no dude en ponerse en contacto con nosotros respondiendo a este correo. Adjunto encontrará la factura en formato PDF y XML. ¡Saludos cordiales! subject: '{alias} - Complemento de pago #{folio}' invoicesEgress: body: >- ¡Hola {cliente}!, Espero que se encuentre de maravilla. Queremos hacerle llegar la factura número {folio} correspondiente a los servicios que le brindamos. ¡Gracias por confiar en nosotros! Le ruego revise detalladamente la factura y, si tiene alguna duda o comentario, no dude en ponerse en contacto con nosotros respondiendo a este correo. Adjunto encontrará la factura en formato PDF y XML. ¡Saludos cordiales! subject: '{alias} - Nota de crédito #{folio}' payments: body: >- Hola {cliente}, por favor realiza el pago correspondiente por la cantidad de {total} {moneda} subject: Solicitud de pago - {alias} paymentsReminders: body: > Hola {cliente}, por favor no olvides realizar el pago correspondiente por la cantidad de {total} {moneda}, quedan pocos días para su vencimiento. Fecha límite de pago: {fechaLimite} subject: No olvides realizar tu pago - {alias} paymentsRemindersAfter: body: >- Hola {cliente}, queremos recordarte que tu pago por la cantidad de {total} {moneda} está vencido desde hace {diasVencido} día(s). Fecha límite de pago: {fechaLimite} Te pedimos regularizar tu pago lo antes posible para evitar contratiempos. Puedes realizarlo desde el siguiente enlace: {linkDePago} Si ya realizaste tu pago, por favor ignora este mensaje. ¡Gracias por tu confianza! subject: Tu pago está vencido - {alias} receipts: body: >- Estimado/a {cliente}, Le agradecemos por su compra. Adjunto encontrará su recibo de ventas correspondiente a la compra realizada el {fecha}. Detalles del recibo: ID de recibo: {recibo} Fecha de la compra: {fecha} Total: {total} Por favor, revise detenidamente la información del recibo. Si encuentra algún error o tiene alguna pregunta, no dude en contactarnos para que podamos corregirlo. Una vez más, gracias por su confianza. Atentamente, {alias} subject: Genera tu factura - {alias} receiptsReminders: body: >- Estimado/a {cliente}, le enviamos este correo para recordarle que aún puede facturar la transacción que realizó el día {paid_date} por un total de {total} {moneda}. Fecha límite para facturar: {fecha_limite}. Si encuentra algún error o tiene alguna pregunta, no dude en contactarnos para que podamos corregirlo. Una vez más, gracias por su confianza. Atentamente {alias} subject: Quedan pocos días para realizar tu factura - {alias} bankReview: body: >- Estimado/a {cliente}, Le agradecemos por su compra. Estamos revisando su pago. Por favor aguarde. ¡Muchas gracias! subject: Estamos revisando su pago en: invoices: body: >- Dear {cliente}, Here is CFDI invoice number {folio} corresponding to the services we provided. Thank you for trusting us! Please review the CFDI invoice carefully and, if you have any questions or comments, do not hesitate to contact us by replying to this email. Attached you will find the invoice in PDF. Best regards! subject: '{alias} - Invoice #{folio}' invoicesComplements: body: >- Dear {cliente}, Here is CFDI invoice number {folio} corresponding to the services we provided. Thank you for trusting us! Please review the CFDI invoice carefully and, if you have any questions or comments, do not hesitate to contact us by replying to this email. Attached you will find the invoice in PDF. Best regards! subject: '{alias} - Payment complement #{folio}' invoicesEgress: body: >- Dear {cliente}, Here is CFDI invoice number {folio} corresponding to the services we provided. Thank you for trusting us! Please review the CFDI invoice carefully and, if you have any questions or comments, do not hesitate to contact us by replying to this email. Attached you will find the invoice in PDF. Best regards! subject: '{alias} - Credit note #{folio}' payments: body: >- Hi {cliente}, please make the corresponding payment for the amount of {total} {moneda} subject: Payment request - {alias} paymentsReminders: body: > Hi {cliente}, please remember to make the corresponding payment for the amount of {total} {moneda}. Only a few days left before it is due. Payment deadline: {fechaLimite} subject: Don't forget to complete your payment - {alias} paymentsRemindersAfter: body: >- Hi {cliente}, we would like to remind you that your payment for the amount of {total} {moneda} has been overdue for {diasVencido} day(s). Payment deadline: {fechaLimite} Please settle your payment as soon as possible to avoid any inconvenience. You can complete it through the following link: {linkDePago} If you have already made your payment, please ignore this message. Thank you for your trust! subject: Your payment is overdue - {alias} receipts: body: >- Dear {cliente}, Thank you for your purchase. Attached you will find the sales receipt for the purchase made on {fecha}. Receipt details: Receipt ID: {recibo} Purchase date: {fecha} Total: {total} Please review the receipt information carefully. If you find any errors or have any questions, do not hesitate to contact us so we can correct it. Once again, thank you for your trust. Best regards, {alias} subject: Generate your invoice - {alias} receiptsReminders: body: >- Dear {cliente}, we are sending you this email to remind you that you can still invoice the transaction you made on {paid_date} for a total of {total} {moneda}. Invoicing deadline: {fecha_limite}. If you find any errors or have any questions, do not hesitate to contact us so we can correct it. Once again, thank you for your trust. Best regards, {alias} subject: >- Only a few days left to generate your invoice - {alias} bankReview: body: >- Dear {cliente}, Thank you for your purchase. We are currently reviewing your payment. Please stand by. Thank you very much! subject: We are reviewing your payment '401': description: Original credential could not be verified '403': description: Current credential scope denied '404': description: Team is unavailable or current membership does not allow reading it '503': description: Verifier configuration or template read unavailable security: - bearerAuth: [] components: parameters: TeamParameter: name: team in: query required: false schema: type: string description: > **gigstack Connect:** Target team ID for multi-team access. Requires gigstack Connect enabled on your team and shared billing account. Also requires the `multipleIssuerAccounts` feature on your plan. Requests targeting a team other than the one your API key belongs to return `403` without it. Only API keys can use it: an OAuth access token sent with another team's id is rejected with `403 Team mismatch with OAuth token`. **Optional — omit it entirely** unless you are acting on another team. It deliberately carries no example value so generated snippets do not emit `?team=undefined`; when the parameter is absent, the team is derived from your API key. **Example:** `?team=team_xyz789` schemas: TeamEmailTemplateCatalog: type: object additionalProperties: false required: - team_id - effect_scope - source - is_nonprofit - english_enabled - templates_by_language - legacy_is_nonprofit - legacy_templates properties: team_id: type: string effect_scope: type: string enum: - team_shared source: type: string enum: - editor_baseline is_nonprofit: type: boolean english_enabled: type: boolean templates_by_language: type: object additionalProperties: false required: - es - en properties: es: type: object additionalProperties: false required: - invoices - invoicesComplements - invoicesEgress - payments - paymentsReminders - paymentsRemindersAfter - receipts - receiptsReminders - bankReview properties: invoices: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string invoicesComplements: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string invoicesEgress: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string payments: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string paymentsReminders: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string paymentsRemindersAfter: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string receipts: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string receiptsReminders: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string bankReview: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string en: type: object additionalProperties: false required: - invoices - invoicesComplements - invoicesEgress - payments - paymentsReminders - paymentsRemindersAfter - receipts - receiptsReminders - bankReview properties: invoices: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string invoicesComplements: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string invoicesEgress: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string payments: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string paymentsReminders: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string paymentsRemindersAfter: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string receipts: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string receiptsReminders: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string bankReview: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string legacy_is_nonprofit: type: boolean description: Exact strict boolean used by the original eight-key editor response. legacy_templates: type: object additionalProperties: false required: - invoiceMessage - invoiceMessageComplements - invoiceMessageEgress - paymentsEmailsTemplate - paymentsReminderTemplate - paymentsReminderAfterTemplate - receiptsEmailsTemplate - receiptsRemindersTemplate properties: invoiceMessage: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string invoiceMessageComplements: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string invoiceMessageEgress: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string paymentsEmailsTemplate: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string paymentsReminderTemplate: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string paymentsReminderAfterTemplate: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string receiptsEmailsTemplate: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string receiptsRemindersTemplate: type: object additionalProperties: false required: - body - subject properties: body: type: string subject: type: string securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: > **Authentication Method:** HTTP Bearer token. The runtime requires the literal `Bearer ` prefix — a bare token in the `Authorization` header is rejected with `401 unauthorized`. **Header Format:** `Authorization: Bearer YOUR_API_KEY` Your API key is a JWT. Live keys operate on live data (`livemode: true`); test keys operate on isolated test data (`livemode: false`). **Get your key at:** [app.gigstack.pro/settings?tab=api](https://app.gigstack.pro/settings?tab=api) **Errors:** credential failures are answered by the authentication layer with a raw `{ "message": … }` body, not the standardized envelope — `401` for a missing, malformed or expired token, `403` for a revoked key or a plan without API access. See the `Unauthorized` and `AuthForbidden` responses. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.