Notifications tab
Path: Vayapin → Settings → Notifications
Configure how VayaPin pushes real-time updates to your store: address changes, new VayaPins created during your checkout, autofill usage, opt-in declines.
Webhook Configuration
Receive real-time push notifications from VayaPin when address data is updated, a new VayaPin is created at checkout, or a customer interacts with the opt-in.
Webhook URL
The endpoint on your site that VayaPin will POST events to.
- Click Use Auto-Generated URL to populate the field with the plugin's built-in receiver:
https://yourstore.com/wp-json/vayapin/v1/webhook - Or set your own endpoint if you want events to land elsewhere (e.g. an external pipeline). You'll be responsible for signature verification and event routing in that case.
Webhook Secret Key
A shared secret used to sign every webhook VayaPin sends. The plugin verifies the signature on receipt and rejects anything that doesn't match.
- Click Generate to create a strong random secret.
- Or paste your own (minimum 32 chars recommended).
- After changing the secret, you must also update it inside your VayaPin dashboard at vayapin.com/developers → Webhooks. Otherwise inbound webhooks will fail signature verification.
Treat the webhook secret like a password. Never commit it to source control or share it in support tickets.
Events to Subscribe
Tick the events your store cares about. Unchecked events are dropped at the VayaPin side and never sent.
| Event | When it fires |
|---|---|
pin.address_updated | A customer updates their VayaPin profile (address, entrance photo, instructions) — their next order on your store can reflect the change. |
pin.created_at_checkout | A new VayaPin was created on your checkout via the opt-in flow. |
pin.autofill_used | An existing VayaPin was successfully resolved and used to autofill the checkout. |
pin.optin_declined | A customer dismissed or unchecked the opt-in checkbox at order confirmation. |
Last Webhook Delivery
A read-only mini-card showing the most recent webhook delivery — its timestamp, status pill, and the HTTP response code your endpoint returned.
For the full searchable history (events, statuses, retries) see the Webhook Logs page. The View Full Log link in this section opens it directly.
