Event webhooks dispatch real-time HTTP POST notifications to your servers whenever key event actions take place: new attendee registrations, captured ticket payments, application approvals, or entrance QR scan validations. URPASS signs each payload with cryptographic HMAC-SHA256 signatures, letting you automate Slack pings, Zapier workflows, CRM synchronization, and badge printing with zero polling delay.
₹29 introductory offer · 0% ticket commission · Cancel anytime
FEATURES
Listen for granular events including attendee.created, payment.captured, attendee.approved, and checkin.recorded.
Every webhook request includes an X-Urpass-Signature header so your endpoints can verify authenticity securely.
Dispatched immediately upon event execution with automatic exponential backoff retries on network failures.
Inspect request headers, JSON payloads, response codes, and retry histories directly in your developer console.
Connect natively to Zapier, Make, Pipedream, Discord, or Slack to notify teams of new VIP ticket sales.
Send test payloads with one click to verify that your webhook receiver endpoint responds with HTTP 200.
HOW IT WORKS
Enter your HTTPS destination URL in the URPASS developer settings.
Choose which actions trigger the webhook (e.g., ticket purchases, check-ins, or cancellations).
Copy your unique webhook signing secret to authenticate incoming POST requests.
Click 'Test Endpoint' to simulate an attendee check-in and inspect the response.
Trigger automated badge printing, Slack alerts, CRM updates, or catering logs on autopilot.
ZERO POLLING OVERHEAD
Constantly querying a server every 5 seconds to detect new ticket sales wastes bandwidth and causes rate limits. URPASS event webhooks push clean JSON data straight to your infrastructure the exact millisecond an event occurs.
PASS SCANNED
Attendee check-in successful
High-profile conventions and trade shows often prefer printing physical name badges on-demand rather than pre-printing thousands of badges that go unclaimed.
When an attendee scans their QR code at an entrance gate, URPASS dispatches a `checkin.recorded` webhook payload to a local server or cloud relay. The receiver extracts the attendee's name, company, and VIP tier, routing a print job to high-speed thermal badge printers located at the turnstile.
To prevent replay attacks and spoofing, URPASS computes a keyed-hash message authentication code (HMAC-SHA256) of the raw payload using your private webhook secret. The signature is transmitted in the `X-Urpass-Signature` header.
Your receiving server computes the same hash using your secret. If the signatures match, you can be 100% certain the notification originated from URPASS and was not intercepted or altered.
Discover how URPASS powers ticketing, digital credentials, and entrance management across different scenarios.
Get started for ₹29 · 0% ticket commission · Up and running in 5 minutes