---
title: "Send a payment reminder"
method: POST
path: "/companies/{company}/invoices/{invoice}/send-reminder"
tags: ["Invoices"]
---

# Send a payment reminder

`POST /companies/{company}/invoices/{invoice}/send-reminder`

## Request

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

Emails a payment reminder to the customer for this invoice. Accepts optional `email`, `subject`, `message`, `cc`, `bcc` overrides.

## Path parameters

- `company` string, uuid, required
- `invoice` string, uuid, required

## Headers

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

## Request body

- SendInvoiceReminderV1Request: Fields of the payment reminder, shared by `POST /v1/companies/{company}/invoices/{invoice}/send-reminder` and `POST /v1/companies/{company}/invoices/{invoice}/reminder-preview`. Every field is optional: without overrides the standard payment reminder template is used.
  - `email` string, email, nullable: Recipient other than the client email.
  - `subject` string, nullable: Custom subject for the reminder.
  - `message` string, nullable: Additional message for the reminder body.
  - `cc` string[], nullable: Carbon copy addresses.
  - `bcc` string[], nullable: Blind carbon copy addresses.
  - `attach_pdf` boolean, nullable: Per-send override for "attach the invoice PDF". If omitted (or `null`), the company default (`email_settings`) is used.
  - `stripe_payment_button` boolean, nullable: Per-send override for the "Stripe payment button". If omitted (or `null`), the company default is used.

## Response `200`

- object
  - `data` InvoiceReminderSent, required: Acknowledgement of sending a payment reminder.
    - `id` string, required: UUID v7 of the invoice the reminder was sent to.
    - `message` 'Recordatorio enviado correctamente.', required: Confirmation message.

## 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.
- `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)