Webhooks are like having a helpful assistant who proactively notifies your application when important notarization events occur. Instead of repeatedly asking, “Has the notarization been completed?”, webhooks automatically tap your application on the shoulder when it happens.Documentation Index
Fetch the complete documentation index at: https://beglaubigt.de/docs/llms.txt
Use this file to discover all available pages before exploring further.
Why use webhooks?
- Real-time updates: Get instant notifications when notarization events are completed.
- Automation friendly: Perfect for integrating notarization workflows seamlessly.
- Efficient: No need to constantly poll the API for updates.
- Reliable: Never miss an important event, even if your system is temporarily down.
Getting started
To start receiving webhooks from Beglaubigt, follow these steps:- Set up a publicly accessible HTTPS endpoint on your server.
-
Register your webhook URL with Beglaubigt (via your dashboard under
/webhooks). -
Implement a handler to process the
notarization.completedevent.
Webhook payload example
Here’s an example of the webhook payload you’ll receive for a completed notarization:Webhook delivery & retries
When your server receives a webhook, it’s like getting a handshake from Beglaubigt. To confirm you received it:- Your endpoint should respond with HTTP status code 200 OK.
Best practices
Handle Beglaubigt webhooks like a pro by following these best practices:- Make handlers idempotent: Ensure receiving the same webhook multiple times doesn’t cause unintended effects.
- Validate webhook signatures: Verify the event’s authenticity to ensure it originates from Beglaubigt.
- Respond quickly: Acknowledge receipt promptly to prevent retries.