Skip to main content
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

Event IDScopeTriggers
merakiwpn.configuration.auditMeraki WPN ContextAny 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

Every delivery carries a JSON array of events. Each event follows the platform’s standard audit envelope: 
{
  "id": "…",
  "eventId": "merakiwpn.configuration.audit",
  "scope": "ORGANIZATION_CTX_MERAKI_WPN",
  "contextId": "…",
  "organizationId": "…",
  "timestamp": "2026-04-19T12:34:56Z",
  "userId": "…",
  "userEmail": "admin@example.com",
  "action": "UPDATE",
  "module": "MERAKI_WPN",
  "changes": [
    {
      "field": "Meraki WPN Group Passphrase",
      "secret": true,
      "before": "***",
      "after": "***"
    }
  ]
}
Fields marked secret (the Meraki API Key, every Pre-Shared Key) are redacted — the webhook payload shows *** for before and after, 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

  • 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

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: six attempts with exponential back-off (2 min → 4 → 8 → 16 → 32 → 64 min). After the sixth failure the delivery is marked FAILED.
  • 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

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.

​
Organization-scope alternative

If you want to subscribe to all EasyPSK changes across every Meraki WPN Context in the Organization at once, create the subscription at Organization scope instead — but note that the Organization-scope event catalogue is narrower than Context-scope. See Organization Webhooks for the cross-Service event list.

Sign In Webhooks

Shared mechanics and the full retry / batch semantics.

Organization Webhooks

Organization-scope subscriptions.