Webhooks reference

Webhooks connect 2mee to your systems in both directions. They share one signing scheme and one envelope style, so once you’ve implemented one direction the other is familiar.

The two directions

Direction	What it is	You implement
Inbound (you → 2mee)	Your systems start or advance a flow.	Signing a request to the ingest API.
Outbound (2mee → you)	A flow reports what happened.	Verifying a signed request at your endpoint.

Both use HMAC-SHA256 over the raw request body, with webhook-id, webhook-timestamp and webhook-signature headers — aligned with the Standard Webhooks conventions, so the behaviour is familiar to anyone who has integrated Stripe, Svix or Segment.

In this section

• Inbound signing & verification — the HMAC scheme, headers and copy-paste verification code in several languages.
• Outbound envelope — the versioned event body and headers 2mee sends you.
• Event types — the catalogue of outbound event types and the versioning rule.
• Retries & idempotency — backoff, dead-lettering, replay, and how to stay exactly-once.

This is a contract

The signing scheme, the envelope and the event types are public commitments. They change by the additive-only, versioned rule.

Setting one up

For step-by-step setup (rather than reference), see generic webhook setup and Connect Segment.