Invoices

Email quarterly ZIP to accountant

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.
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

Path parameters

companystring uuid required

Public identifier (UUID v7) of the company. Get it from GET /v1/me (data.scope[].id).

Headers

Idempotency-Keystring required
Example:01928f10-7c0e-7c4a-9b7d-2f8a6e3c1d4b

Client-generated opaque key (up to 255 characters; UUID v7 recommended) that makes retries safe: the first response is cached and replayed for repeats without re-executing the mutation. Reusing a key with a different body returns 422 idempotency_key_reused; the values of secret fields (password, secret…) count as part of the body, so retrying with a corrected secret under the same key is a different request, never the replay of the earlier answer. See the Idempotency guide. Required on this operation: repeating it delivers an effect that cannot be taken back (an email sent, a file generated, a third-party call, a charge), so a request without this header is rejected with 422 idempotency_key_required before any business logic runs.

Factuarea-Versionstring date
Example:2026-06-01

Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.

Request body

yearinteger required
quarterinteger required
include_indexboolean nullable
include_non_invoiced_chargesboolean nullable
emailstring email nullable
messagestring nullable

Response

Example response

{
  "data": {
    "message": "Email trimestral encolado correctamente.",
    "year": 2026,
    "quarter": 1,
    "recipient": "contable@empresa.example"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.