Skip to content

Webhooks

If you run other software (a fulfilment platform, a print partner’s system, your own dashboard), webhooks are how Sigmira keeps it in the loop without anyone refreshing a page. The instant something happens, like a print file being ready, Sigmira sends a message straight to a web address you control, and your system reacts. It’s the most hands-off way to wire Sigmira into the rest of your operation. This is an advanced, developer-flavoured feature, so if you’re not connecting Sigmira to other tools you can comfortably skip it.

What webhooks are for

As the Webhooks page puts it: Push exports and other events to your fulfilment platform — no polling. When something happens in Sigmira, it sends a message to a web address (URL) you control, and your system reacts. If you don’t integrate with other software, you can ignore this page entirely.

Add a webhook

  1. Open Webhooks and click + Add webhook.
  2. Fill in the Add webhook form:
    • Endpoint URL — where Sigmira should send the event.
    • Description (optional) — a note for yourself.
    • Events — which events to send: Export delivered and/or Export failed.
  3. Click Save webhook.

Your signing secret

Right after creating a webhook, Sigmira shows a signing secret once: This is the only time we’ll show this signing secret. We store a hash, not the value — if you lose it, rotate the secret from the webhook detail page. Copy it somewhere safe.

Your receiving system uses this secret to verify each message really came from Sigmira, by checking the Sigmira-Signature header. (If you’re not the one building that integration, hand the secret to whoever is.)

Managing a webhook

Open a webhook to see its Endpoint details (URL, Signing secret, Events, Enabled) and:

  • Send test event — fire a sample so your integrator can confirm it’s wired up.
  • Rotate secret — issue a New signing secret. The previous one stays valid for an overlap window, so your system has time to switch over without missed events.
  • Delete — remove the webhook.

A Recent deliveries table logs each send (Event, Status, Attempt, Duration, When) so you can spot failures.

Next