Registration

Two switches must both be on before you receive anything. They live on different objects, and a silent no-events situation is nearly always one of the two rather than a problem with your receiver.

	Set on	What it is
Destination	the short code	The URL we POST to, and the signing secret.
Enablement	each service	Whether that service emits events at all.

So one short code has one destination, and each service on it independently decides whether it contributes. A service with events enabled but no destination on its short code sends nothing, and so does a short code with a destination whose services are all disabled.

Both are configured by the operator team.

What you need to provide

• An HTTPS endpoint that accepts POST and returns quickly.
• The addresses we should reach it on, if your firewall restricts inbound traffic.

Your signing secret

A secret is minted for your short code when the destination is first configured. It is shown once. Store it before you close the dialog: it cannot be displayed again, only rotated.

Rotation invalidates the old secret, so plan a brief window where your receiver accepts either, or coordinate the switch.

Before you go live

Test your receiver end to end rather than by inspection. There is no echo endpoint yet: the operator team can point a test short code's destination at your URL and drive a real opt-in on a test service, which exercises the whole path including the signature.