Webhooks Overview - That's Me Docs

Webhooks let That’s Me notify your system when something happens — no polling required.

How it works

You register an endpoint URL (your N8N/Make/Zapier webhook URL, or your server)
You choose which events to receive
When the event occurs, That’s Me sends an HTTP POST to your URL within seconds
If delivery fails, That’s Me retries automatically (3 attempts: 1min, 5min, 30min)

Supported events

Event	When it fires
`certificate.issued`	A certificate is emitted to a recipient
`certificate.accepted`	A recipient accepts their certificate
`certificate.rejected`	A recipient declines their certificate
`certificate.expired`	A certificate passes its expiration date
`recipient.registered`	A recipient who had a pending certificate creates an account

Payload structure

Every webhook delivery has the same envelope:

{
  "event": "certificate.issued",
  "created_at": "2026-03-18T10:30:00Z",
  "data": {
    // event-specific fields
  }
}

Verifying signatures

Every request includes the header X-TM-Signature. You should verify this to confirm the request came from That’s Me. See Verify Signatures for implementation examples.

Delivery headers

Header	Value
`X-TM-Signature`	`t=timestamp,v1=hmac_sha256_signature`
`X-TM-Event`	Event type (e.g. `certificate.issued`)
`X-TM-Delivery`	Unique delivery UUID
`Content-Type`	`application/json`