---
title: "Email quarterly ZIP to accountant"
method: POST
path: "/companies/{company}/invoices/quarterly/send-email"
tags: ["Invoices"]
---

# Email quarterly ZIP to accountant

`POST /companies/{company}/invoices/quarterly/send-email`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/invoices/quarterly/send-email`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Generate the quarterly ZIP and email it to a recipient, typically the tax accountant.
- Unless `include_non_invoiced_charges` is `false`, it adds a CSV of charges left out of invoicing and their refunds.
- A quarter with only such charges yields a CSV-only ZIP.

## Path parameters

- `company` string, uuid, required

## Headers

- `Idempotency-Key` string, required
- `Factuarea-Version` string, date

## Request body

- QuarterlyDownloadV1Request: Public REST API v1 — POST /v1/companies/{company}/invoices/quarterly/download-zip and POST /v1/companies/{company}/invoices/quarterly/send-email (shared fields). The canonical recipient field is `email`. We accept `to_email` as a deprecated alias for compatibility with older clients.
  - `year` integer, required
  - `quarter` integer, required
  - `include_index` boolean, nullable
  - `include_non_invoiced_charges` boolean, nullable
  - `email` string, email, nullable
  - `message` string, nullable

## Response `200`

- object
  - `data` object, required
    - `message` 'Email trimestral encolado correctamente.', required
    - `year` integer, required
    - `quarter` integer, required
    - `recipient` string, required

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company. `profile_not_found`: the company in the path does not exist, is not in the API key scope or belongs to the other environment (live or test).
- `422`: Validation failed, or the invoice cannot undergo the requested state transition (e.g. marking an already-paid invoice as paid, or editing an issued invoice — use a corrective instead). The `error.param` field identifies which input is invalid, if any. Issuing or annulling an invoice can also be rejected with `verifactu_not_eligible`: either a field of the invoice does not fit its billing record, or — only when the company has VeriFactu enabled in NO VERI*FACTU mode — it has no usable signing certificate (`error.subcode: signing_certificate_unavailable`; `error.param` is `certificate`, `representation` or `system_certificate`, depending on what is missing); in both cases the invoice stays exactly as it was.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)