Skip to main content

Webhooks

Webhooks let you receive validation results asynchronously. Instead of blocking your application on a VIES, HMRC, or BFS lookup, submit the request and get the result delivered to your endpoint when it is ready. Available on Pro and Business plans. Avatcado signs every webhook delivery with HMAC-SHA256 so you can verify it came from Avatcado.

Setup

  1. Configure your webhook URL in the dashboard or via the API (PUT /v1/webhooks/config)
  2. Your endpoint must accept HTTPS POST requests
  3. Your endpoint should return 2xx within 10 seconds
  4. Avatcado logs every delivery attempt. You can view delivery history and replay failed deliveries from the dashboard.

Event types

Event payloads

validation.completed

validation.failed

batch.completed

test

Verifying signatures

Every delivery includes these headers:
  • X-Avatcado-Signature: sha256=<hex digest>
  • X-Avatcado-Timestamp: Unix timestamp (seconds)
  • X-Avatcado-Event: event type
  • X-Avatcado-Delivery-Id: unique delivery identifier
During the brand transition we also send the legacy X-Vatly-* headers with identical values, so existing integrations keep working unchanged. The legacy headers are deprecated and will be removed after 2026-07-01. Move your verification to the X-Avatcado-* headers before then.
The signature is computed as HMAC-SHA256 of {timestamp}.{body} using your signing secret. Always verify signatures before processing webhooks. Check the timestamp is within 5 minutes to prevent replay attacks.

Retry behavior

If your endpoint returns non-2xx or times out, the delivery is logged as failed. You can replay failed deliveries from the dashboard. The underlying async validation is handled separately. Queue delivery to the background worker is retried up to 5 times with exponential backoff. If an upstream registry is down, the worker consults the national tax register where one exists (unless the request was submitted with fallback: false) and serves its answer when it confirms the number (meta.source_status: "fallback"), then the most recent stored result where one exists (meta.source_status: "unavailable"); otherwise it marks the validation as failed, sends a validation.failed webhook, and refunds the validation to your quota. Webhook delivery and validation processing are independent. A failed delivery does not trigger a re-validation.

Best practices

  • Return 2xx quickly. Do heavy processing in the background after acknowledging the webhook.
  • Verify signatures on every request. Never trust unverified payloads.
  • Handle duplicate deliveries gracefully. Replays send the same payload with a new delivery ID.
  • Store the X-Avatcado-Delivery-Id header for debugging and deduplication.