What happens if my server does not respond?

A 2xx response closes the delivery. 408, 425, 429, 5xx and transient silence enter the retry queue with growing backoff and jitter; other 4xx responses become permanent failures.

How do I avoid processing the same notification twice?

Store the stable event identifier before running external effects. If it arrives again through a retry or manual replay, return 2xx without repeating the work.

Can I test webhooks without touching production?

Sandbox records events but only sends ping externally to test connectivity and signatures. To test a catalog event with test_event, use an endpoint in a live company. The event is marked as a test.

Can I rotate the secret without losing events?

For 24 hours, deliveries include signatures with both the previous and new secrets. Rotate the secret and update your receiver within that window. Both SDK verifiers can validate either signature in the header.

Factuarea webhooks

Invoicing webhooks. Your business responds to change

A paid invoice, an approved quote or a received payment can start your next process. Connect your ERP, CRM or application with signed Factuarea events.

Start free Read the guide

HMAC-SHA256 signatures
Automatic retries
Query and replay through the API

Compatible integrations and formats

Webhooks · Active endpoint

Endpoint subscriptionsChoose a change to listen for

InvoiceF-2026-142Paid

POST · HMAC-SHA256

Your application/webhooks/factuarea

200 OK

Your ERP can update the customer balance.

Event ID01931b3e…8a0d

Event-driven automation

From a change in Factuarea to a workflow in your business

Subscribe an HTTPS URL to the events you need. Factuarea sends a signed POST with the event and its data; your application uses them to carry out the next step.

Keep your ERP up to date

Update documents and balances when invoices are created or paid, without repeatedly checking for changes.

invoice.createdinvoice.paid

Connect sales, payments and follow-up

Use an approved quote or a received payment as a signal for your CRM, reconciliation or customer service tasks.

quote.approvedpayment.received

Track VeriFactu record submissions

React to a submission or failure and query the fiscal record for its status. A submission event does not replace checking acceptance.

invoice.verifactu_submittedinvoice.verifactu_failed

These connections are built through your receiver: choose which events to process and how they become actions in your system.

Explore the event catalog

Delivery under control

When your server fails, you can follow the trail

Inspect the HTTP response, attempt and next retry. After resolving the issue, you can replay a delivery through the API.

Up to eight attempts per delivery
Network failures, 5xx, 408, 425 and 429 responses retry with backoff. Other 4xx responses stop that delivery so you can fix the receiver.
One event, even if it arrives more than once
The event ID stays stable. Store it to deduplicate; a manual replay creates another delivery for that same event.
Recover context through the API
The event log lets you query the last 30 days. If an endpoint is degraded, a ping with a 2xx response lets you recover it.

Configure retries and replays

Delivery loginvoice.paid

Your server’s response

First attempt14:32:00 · POST

503

Retry scheduledIn approximately 1 minute.

Event ID01931b3e…8a0dDelivery ID01931b3e…8a0c

Retry scheduled

Delay after each failed attempt

1 min5 min30 min2 h12 h1 d3 d

Base intervals with ±10% jitter.

A receiver that verifies before acting

Verified signatures. Secrets you can rotate

Use the raw body, the Factuarea-Signature header and the endpoint secret. The SDKs check HMAC-SHA256 and a default timestamp tolerance of five minutes.

Verify the signature

import { verifyWebhook } from "@factuarea/sdk";

// Request / Web API
const rawBody = await request.text();
const signature = request.headers.get("Factuarea-Signature") ?? "";

const event = verifyWebhook(
  rawBody,
  signature,
  process.env.FACTUAREA_WEBHOOK_SECRET!,
);
console.log(event.id, event.type);

An invalid signature makes the verifier throw. Handle that error before processing the event; persist or queue the work, then respond with 2xx.

Rotate without changing your URL

For 24 hours, signatures use both the new and previous secrets. Update your receiver within that window to keep verification working.

Previous24 hNew

Review secret rotation

Test each part of the journey

In sandbox, events are recorded and external delivery is limited to ping. In a live company, test_event sends a catalog event marked as a test through the delivery pipeline.

pingConnection and signaturetest_eventReceiver logic

See what sandbox supports

Choose your connection

An integration that fits your stack

Work with an SDK, explore the API contract or connect your assistant. Choose your tool to find the right starting point and documentation.

Compatible technologies and clients

Your tool → Factuarea

Payments and invoicing

Connect payments and invoicing

Learn which Stripe events Factuarea processes and how they relate to invoices. Review the configuration and limits of each workflow.

Stripe → FactuareaConnect Stripe

API operations: 595
resources: 50
MCP tools: 581
documentation pages: 1306

Before going live

Common webhook questions

Verify the Factuarea-Signature header with HMAC-SHA256, the unmodified body and a five-minute tolerance. The official SDKs include the verifier to avoid serialisation differences.

A more connected business

Make every change reach your system

Prepare your receiver, choose events and verify the connection with a ping. The documentation covers everything from signatures to recovering deliveries.

Start free Read the webhooks guide