Email domain verification failed
Delivered when a sending domain of your account changes to FAILED. It is sent once per transition, only
to the live endpoints of the account that owns the domain; the account that manages it does not receive
it. The event belongs to the account, so company_id and nif are not set (absent or null).
Trigger: the DNS records of the domain could not be verified. previous_status tells the two cases
apart: PENDING means the domain never verified; VERIFIED means it was verified and stopped passing
the check.
Recommended actions:
- Check that the records in
dns_recordsare published exactly as shown, then request a new check withverifyAccountEmailDomain. - If
previous_statusisPENDING, do it before the domain is removed, 72 hours after it was registered. A domain that was onceVERIFIEDis not removed for that reason. - Until the domain is
VERIFIEDagain, do not rely on it for sending.
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"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"email_domain.failed"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 email_domain.verified and email_domain.failed events: the email domain as it is after the
change, with the status it had before. On email_domain.failed, previous_status PENDING means the
domain never verified and VERIFIED means it stopped passing the check.
Response Body
NIF created
Delivered when an account holder you provisioned registers their first (or an additional) NIF (company) during onboarding. **Always verify `BeeL-Signature` before processing.**
Email domain removed
Delivered when a sending domain of your account is removed. It is sent once per removal, only to the live endpoints of the account that owned the domain; the account that manages it does not receive it. The event belongs to the account, so `company_id` and `nif` are not set (absent or `null`). **Trigger:** the domain is no longer in the account. `reason` says why: `EXPIRED`, `DELETED_BY_USER` or `DELETED_AT_PROVIDER`. The payload carries the domain as it was at removal and has no `previous_status`. **Recommended actions:** - Stop treating the domain as available for sending. If `is_default` is `true`, the account's emails go out from BeeL until you set another default with `setAccountEmailDomainDefault`. - `EXPIRED` and `DELETED_AT_PROVIDER`: register the domain again with `createAccountEmailDomain` if you still want it. `DELETED_BY_USER`: none, unless the deletion was not intended. **Always verify `BeeL-Signature` before processing.**