Webhooks overview

Webhooks let you receive HTTP notifications whenever something happens in your Pepvote account. When a voting event starts, a vote is cast, a voter registers, or a payment succeeds, Pepvote sends a POST request to a URL you configure with the event details.

What you can do with webhooks

• Sync vote results to a Google Sheet or database
• Post voting event updates to a Slack or Discord channel
• Trigger workflows in Zapier, Make, or n8n
• Update your CRM when a new voter registers
• Send custom notifications when voting starts or ends

How it works

1. You create a webhook endpoint in your Pepvote dashboard and provide a URL.
2. You choose which event types the endpoint should receive.
3. When a matching event happens, Pepvote sends a signed HTTP POST to your URL.
4. Your server verifies the signature and processes the event.

Every request includes a cryptographic signature so your server can confirm the request came from Pepvote and was not tampered with.

Requirements

• Your endpoint URL must use HTTPS.
• Each account can have up to 2 account-level webhook endpoints.
• Each voting event can have up to 2 event-level webhook endpoints that override the account-level ones.

Next steps

• Managing endpoints to create, edit, and delete webhook endpoints.
• Event types for the full list of events you can subscribe to.
• Payload format to understand the request structure.
• Verifying signatures to authenticate incoming requests.
• Delivery and retries to understand retry behavior and failure handling.