One endpoint, many events
Subscribe a single receiver to everything it cares about, or split events across receivers — a stock service and an accounting service can each take only what they handle. You may register up to ten.
Webhooks
The other direction. Instead of your software asking Localoy what changed, Localoy POSTs a signed JSON event to a URL on your server the moment it happens.
Register a receiver under Webhook Endpoints on the API Credentials page, or over the API at /api/v1/open-network/webhooks with your partner session. An endpoint is a URL plus the list of events it wants, and it comes with a whsec_… signing secret that is yours alone.
Sandbox and production are separate
An endpoint belongs to one environment and only ever receives events from that side, so a staging receiver cannot be woken by live traffic. Bookings and payments are real customer activity and are always production. The environment cannot be changed afterwards — register a second endpoint instead.
Your receiver must be public and https
The URL is checked when you save it and again before every single delivery: a host that resolves to a private, loopback or link-local address is refused, and redirects are never followed. If your receiver sits behind a tunnel during development, point the endpoint at the tunnel's public https URL rather than at localhost.