Webhooks
Subscribe to the configuration-audit event stream for a Meraki WPN Context and keep your SIEM or change-management system in sync with admin actions.
EasyPSK emits a single webhook event — configuration-audit — at Meraki WPN Context scope. Subscribing lets you mirror every configuration change made by an admin (or by a Self-Service Group Administrator on behalf of their unit) into the system of record you actually trust for this kind of data: a SIEM, an audit archive, a change-management workflow, or your building-management platform.
The one event
Section titled “The one event”| Event ID | Scope | Triggers |
|---|---|---|
merakiwpn.configuration.audit | Meraki WPN Context | Any admin-side or Group-Administrator-side configuration change in the Context — integration updates, WPN create / rename / remove, Pre-Shared Key rotation, Self-Service User add / modify / revoke, Self-Service Enrollment toggles, Administrator changes. |
Lifecycle events for connected devices — device joined, device left, device moved — are not webhook events in EasyPSK. The Meraki dashboard owns that data and exposes it through its own integrations; EasyPSK doesn’t re-publish it on this bus.
Payload shape
Section titled “Payload shape”Every delivery carries a JSON array of events. Each event follows the platform’s standard audit envelope:
- An event type — the event id (
merakiwpn.configuration.audit). - A created timestamp for when the change happened.
- A scope object that identifies the Organization and the Meraki WPN Context the change belongs to.
- An identifier for the actor and origin of the change (the acting user, and, where relevant, the source IP address and device MAC).
- A data object carrying the audit detail: a list of property changes, each with the property that changed and its old and new value.
The exact field layout is best confirmed from a live delivery: the Recent Deliveries tab on the subscription shows the precise Request body sent to your receiver.
Secret values (the Meraki API Key, every Pre-Shared Key) are redacted — the webhook payload shows a masked placeholder for the old and new value instead of the real secret, matching what the Audit Log displays on the admin side. That’s intentional: the webhook stream is designed to be safe to ship into a general-purpose SIEM.
Typical use cases
Section titled “Typical use cases”- Audit archive. Forward every event to an immutable store (S3 with object lock, a write-only Elasticsearch index, etc.) for lease-compliance and landlord-tenant-relationship evidence.
- Building-management integration. When a lease in your PMS ends, automatically revoke the Group Administrator role for that apartment’s Self-Service User — and use webhook events the other way to confirm the revocation happened.
- Change review. Stream events into a channel the facilities team watches, so a Group Administrator rotating their PSK three times an hour triggers a quick check-in call.
Delivery mechanics
Section titled “Delivery mechanics”Shared with every other Service:
- Events are delivered in batches — one HTTP POST with a JSON array.
- Default batching: 20 minutes or 20 000 events, whichever comes first. Configurable per subscription.
- Retry on non-2xx: the platform retries with an increasing (exponential) back-off, starting at one minute and doubling each retry. After the final retry fails the delivery is marked FAILED and no further attempts are made for that delivery.
- Delivery history retained for 3 days on the Recent Deliveries tab of the webhook subscription. Inspect the Request / Response pair per attempt to debug 4xx/5xx responses from your receiver.
See Sign In Webhooks for the shared delivery-engine behaviour in detail — it applies identically to EasyPSK.
Setting up a subscription
Section titled “Setting up a subscription”Open Administration → Webhooks in the Meraki WPN Context, then Create Webhook. You’ll set:
- Name and optional description — identifies the subscription in the list.
- Endpoint URL — the receiver that will accept the POST.
- Content type — typically
application/json. - Custom HTTP headers — for shared-secret authentication to your receiver.
- Enabled events — pick
merakiwpn.configuration.audit. It’s the only one available at this scope. - Batch settings — override the 20 min / 20 000-event defaults if your receiver prefers smaller, more frequent batches.
After saving, the Pending Events tab shows the queue building up, and the Recent Deliveries tab shows each POST once it fires.
No Organization-wide EasyPSK feed
Section titled “No Organization-wide EasyPSK feed”A webhook at the Organization scope subscribes only to
organization.configuration.audit — changes at the Organization
layer (Organization Settings, Administrators, Service Context
create / rename / remove, and similar). It does not carry the
per-Context merakiwpn.configuration.audit stream, so it will not
show you the in-Context EasyPSK changes documented above (WPN
create / rename / remove, key rotation, Self-Service User changes,
integration updates).
To capture configuration changes inside a Meraki WPN Context, create the subscription in that Context (Administration → Webhooks, as described above). If you operate several Meraki WPN Contexts, create one subscription per Context — there is no single Organization-scope subscription that fans in every Context’s audit stream. See Organization Webhooks for what the Organization-scope feed does cover.