Webhooks
Mountaya records every change in your organization as a webhook event: a member's role changed, an itinerary published, an invoice paid. It sends each event, signed, to the https endpoints you register.
Event
- Create an endpoint and pick the event types it is sent.
- Verify the signature of each delivery, on the raw body.
- Answer
2xxwithin 10 seconds, then process the event.
- At least once. One event can arrive twice. Deduplicate on its
id. - In no promised order. Order one resource's events by the
versionits object carries, or read the resource. - Lean payloads.
data.objectholds identifiers and short fields, never geometry or credentials. - Retried for about 72 hours. After that, recover what you missed: events stay listed for 13 months.
Every event arrives in the same envelope.
Event types documents every field and every type.
The Map Studio API's …/events streams serve open editors. They push changes while a client holds the connection, and keep almost nothing. Webhook events serve your servers: Mountaya keeps them, signs them, and retries until your endpoint answers.
Use both: a stream to refresh what a person is looking at, webhook events to keep your systems in step.