Announcing Multiple Webhook Endpoints

You can now register more than one events webhook on a Pingram account. Route delivery, opens, clicks, failures, and inbound traffic to different systems — your CRM, a support tool, and an internal worker — without a single catch-all URL.

Why this exists

A single webhook URL is enough when one service owns every event. Most teams outgrow that quickly: billing wants failures, product wants opens and clicks, and inbound replies belong in a different pipeline. Until now you had to fan those events out yourself.

What you get

• Multiple endpoints — add up to ten HTTPS URLs, each with its own event list
• Per-endpoint secrets — every endpoint has its own pingram_whsecret_… signing key
• Dashboard or API — manage them from the Webhook page, or with webhooks.listWebhooks, createWebhook, updateWebhook, and deleteWebhook

Existing single-URL configurations keep receiving events. Update or add endpoints when you are ready.

API

await pingram.webhooks.createWebhook({
  webhook: 'https://your-api.com/webhooks/pingram',
  events: ['EMAIL_DELIVERED', 'EMAIL_OPEN', 'EMAIL_FAILED']
});

Routes:

GET    /webhooks
POST   /webhooks
PUT    /webhooks/{endpointId}
DELETE /webhooks/{endpointId}

Getting started

1. Open Webhook in the dashboard
2. Click Add endpoint, enter an HTTPS URL, and pick the events that endpoint should receive
3. Save the signing secret and verify incoming requests

See Events Webhook and the webhook skill for event types, payloads, and signature verification.