Invoice reply received
Delivered when a reply of a customer about an invoice is stored, on any channel and also
when you register it. Only to the endpoints of the account that owns the company, never to
an account that manages it, which can still read the replies with
GET .../invoice-replies. It carries a masked excerpt, subject and sender.address;
read the reply for the full text.
Recommended actions:
- Show the reply next to its invoice, routing on
channel. - Subscribe to
invoice.reply.deletedif you keep a copy.
Always verify BeeL-Signature before processing.
Header Parameters
HMAC-SHA256 signature. Format: t=<unix_timestamp>,v1=<hex_signature>
Verify this before processing any event (see spec description for algorithm).
^t=\d+,v1=[0-9a-f]{64}$Canonical event type identifier (matches the type field of the payload).
"verifactu.status.updated" | "invoice.issued" | "invoice.email.sent" | "invoice.pdf.generated" | "invoice.voided" | "recurring_invoice.paused" | "invoice.schedule_failed" | "account.claimed" | "company.created" | "representation.signed" | "email_domain.verified" | "email_domain.failed" | "email_domain.removed" | "connection.connected" | "connection.disconnected" | "invoice.reply.received" | "invoice.reply.deleted" | "invoice.email.bounced"UUID of the logical webhook event. Identical across all retry attempts.
Matches the id field in the payload. Use this for idempotency deduplication.
uuidUUID of this specific delivery attempt. Unique per HTTP call, even for retries of the same event. Use this to correlate with delivery logs in the BeeL. dashboard.
uuidSame value as BeeL-Event-Id. Standard idempotency header for deduplication.
uuidUnique identifier of this webhook event delivery.
uuid"invoice.reply.received"ISO-8601 timestamp when the event was created.
date-timeBeeL. API version that generated this event.
Deprecated in favour of the TEST/PROD environment vocabulary: livemode: true is equivalent to environment PROD.
true only for test deliveries triggered manually from the BeeL. dashboard.
Unique identifier (UUID) of the company the event is about, or null when not scoped to a specific company. A single endpoint receives events for every company it manages (multi-NIF / accounting firms); route on this field.
uuidNIF of the company the event is about (human-readable identifier).
Account the event happened in. For your own events this is your account; for events of accounts you manage it identifies which one. Route on this field together with account_external_ref.
uuidYour own identifier for that account, as supplied when you provisioned it (external_ref). Lets you map the event onto your internal record without an extra lookup. null for accounts you did not provision.
How account_id relates to you: own when the event happened in your own account, managed when it happened in an account you manage. Same field name and vocabulary as the account_relationship you set on POST /v1/webhooks to choose which of these you receive (own by default; all there means both).
"own" | "managed" | nullPayload for invoice.reply.received events: the reply as a summary. subject, excerpt
and sender.address are masked, and it carries no external_id, sender name or file
names. The full reply is in GET /v1/companies/{company_id}/invoice-replies/{reply_id}.
Response Body
Recurring invoice paused
Delivered when a recurring invoice (schedule) stops generating **without anyone asking for it** — a plan downgrade or an unattended generation that failed with something waiting will not fix. A schedule paused by a person is not delivered: whoever paused it already knows. **Why this matters:** the invoice that schedule was going to issue this period will not arrive. If your billing depends on it, nothing else will tell you — the account holder may never open the dashboard. **Trigger:** the daily generation batch pauses the schedule. **Recommended actions:** - Stop expecting that invoice for the current period. - If `reason` is `GENERATION_FAILURE`, fix the `blocker` (it is the same vocabulary the emission API returns in a 422 `EMISSION_NOT_READY`) and resume the schedule. **Also delivered in Test.** Sandbox is a faithful rehearsal of the mechanism, so you can see this failure mode before it happens in Live. **Always verify `BeeL-Signature` before processing.**
Invoice reply deleted
Delivered once when the company deletes a reply, usually to answer an erasure request. Only to the endpoints of the account that owns the company. It carries identifiers only. **Recommended actions:** - Erase what you stored about the reply from earlier `invoice.reply.*` events. - Discard an `invoice.reply.received` with the same `reply_id` that arrives after it. BeeL. stops sending it once the reply is deleted, but a retry already scheduled can still arrive. **Always verify `BeeL-Signature` before processing.**