Webhooks

Your system is told what happened, and told again if it missed it

Meeting started, meeting ended, attendance settled, recording ready — signed, retried, and dead-lettered rather than dropped.

What it is

Four events, sent to a URL you nominate, each signed so you can verify it came from us and has not been altered.

Retried with a growing gap if your endpoint is down, and after the last attempt it goes to a queue somebody can see rather than disappearing.

Why the dead letter matters more than the retries

Every webhook system retries. The failure that hurts is the one where an integration has been receiving nothing for three weeks and nobody knows — because "no events" and "no events arrived" look identical from the receiving end.

Read next

  • A real API

    Create meetings, add people, read attendance and sign somebody in — versioned, and documented by a specification that cannot drift from the implementation.

  • It goes back where it came from

    Automatically, as well as exporting — so nobody reconciles two lists a week later.

  • Mail that arrives

    Invitations, reminders and minutes, with retries, a queue somebody can look at, and an unsubscribe that works without signing in.

Everything it does

Want to see this working?

Tell us what you are trying to do with it and we will show you that, rather than a tour of everything else.

info@seeuall.com
    Webhooks — SeeUAll · SeeUAll