Webhooks
Form Submitted
Webhook triggered when a pass form is submitted
WEBHOOK
New to pass issuance forms? See the Custom Pass Issuance Forms guide.
- Answers – every field on the form, in the order shown. Dates are always in ISO8601 format (
YYYY-MM-DD). The pass inincludedshows values as saved on the pass, so dates there use the date format chosen on the form field. - Non-pass fields – answers with
nonPassField: truearen’t saved on the pass. This webhook is the only place you get them. - Consents – a copy of the consent text the person saw.
checkboxmeans they ticked the box to agree,noticemeans the text was shown without a checkbox. - Telling forms apart – use
form.templateId. The formslugcan be changed in the dashboard. - Answers are not stored – PassEntry doesn’t keep form answers after the webhook is delivered. If your endpoint keeps failing until the last retry, the answers can’t be sent again.
Authorizations
The X-Webhook-Signature header is generated using the webhook payload and shared secret key.
To verify that the webhook is authentic, you can encrypt the webhook payload using the SHA-256
encryption algorithm and your secret key.
If your generated signature matches the signature included in the X-Webhook-Signature
header, you can confirm that the webhook is authentic.
Body
application/json
Response
200 - application/json
Return a 200 status to indicate that the data was received successfully