Webhooks

EasyPSK publishes one event type over webhooks.

Event	Scope	Emitted when
merakiwpn.configuration.audit	Meraki WPN context	Any configuration change in the context, made by an administrator or by a group administrator in the Self-Service portal

That covers the integration settings, the Wireless Personal Networks themselves, key rotation, and changes to self-service users. The event records what changed, who changed it, and when. Keys are redacted in the payload.

What is not streamed

Device lifecycle is not a webhook event in EasyPSK. A device joining, leaving or moving is data the Cisco Meraki dashboard owns, and it is exposed through Meraki’s own integrations. EasyPSK does not republish it.

An integration that needs to react to devices connecting should therefore be built against Meraki, and this stream used for the configuration side: who changed which network, and when.

Delivery

Destination, scope, instant or batched delivery, the secret token, retries and the delivery history are the same across every service and are described under Integrations.

Related

• Administration: where the configuration changes these events describe are made.
• Logging, Reporting, and Retention: the in-portal audit record.