Webhook endpoints
An endpoint is an https URL of yours that Mountaya sends webhook events to. An organization holds 2 of them unless its agreement says otherwise, 6 at most. Its owners and admins manage them.
- Open Organization → Webhooks, then the Endpoints tab.
- Select Add endpoint. Enter the URL, then pick the event types it is sent.
- Copy the signing secret it shows, and store it on your server as
MOUNTAYA_WEBHOOK_SECRET. An owner or an admin can reveal it again on the endpoint's page.
The same page lists every event and every delivery, and shows how reliably each endpoint receives them.
Use a key that carries the management scope, and a session token naming an owner or admin. Your organization's id is in the Mountaya app's address, after /organizations/.
enabled_events lists what an endpoint is sent. Each entry takes one of three forms.
A family stops at its own name. collection.* sends collection.created, never collection.itinerary.added: add collection.itinerary.* for that. Event types lists every family.
Set status to disabled to stop deliveries, and back to enabled to resume them from the next event.
Events recorded while an endpoint is disabled are not sent when you enable it again. Before you enable it, read its failing_since, then redeliver from that moment if you need them.
Deleting an endpoint stops its deliveries and frees its place under your agreement's limit. Its past deliveries stay readable, and you can still filter them by its id.
- In the Mountaya app: the organization's owners and admins.
- Through the API: a key carrying
management, with a session token naming an owner or admin.
Revealing or rotating a secret is done in the Mountaya app only.