Skip to main content
This guide walks you through creating a bucket, adding a forwarder, and verifying that a webhook event reaches your application. By the end you will have a working ingestion pipeline you can point any webhook provider at.

​
Prerequisites

  • A Repost account (free tier works for this guide)
  • An HTTP endpoint that can receive POST requests (your API, a test server, or a local machine using the CLI)

​
Step 1: Create a bucket

A bucket is the URL you give to a webhook provider. All events from that provider flow through this bucket.
1

Open the dashboard

Go to app.repost.sh and sign in.
2

Click Create bucket

Choose Queue mode for most integrations. Queue mode acknowledges the provider immediately and delivers events asynchronously, which is what most providers expect.
3

Name your bucket

Use a descriptive name like stripe-production or github-events. Repost generates a unique URL from this name.
4

Copy the bucket URL

After creation, copy the bucket’s public URL. This is the endpoint you will give to your webhook provider.
Use separate buckets for separate providers and environments. For example, stripe-production and stripe-staging are easier to operate than a single mixed bucket.

​
Step 2: Add a forwarder

A forwarder connects your bucket to a destination. Without a forwarder, Repost records events but does not deliver them anywhere.
1

Open the bucket and click Add forwarder

From the bucket detail page, click Add forwarder.
2

Choose External or Internal

  • External — sends events to a public HTTP or HTTPS endpoint (your production or staging API)
  • Internal — holds events for a CLI session on your local machine (see Local Forwarding)
3

Enter the destination URL

For an external forwarder, enter your API’s webhook endpoint, for example https://api.example.com/webhooks/stripe.
4

Save

The forwarder is active by default. New events will be delivered immediately.

​
Step 3: Point your provider at the bucket URL

In your webhook provider’s settings, replace any existing webhook URL with the bucket URL you copied in Step 1. The exact location varies by provider:
ProviderWhere to set the webhook URL
StripeDashboard → Developers → Webhooks → Add endpoint
GitHubRepository Settings → Webhooks → Add webhook
ClerkDashboard → Webhooks → Add endpoint
Any providerLook for “Webhook URL” or “Endpoint URL” in the integration settings

​
Step 4: Verify the event arrived

Send a test webhook from your provider, or trigger a real event (for example, create a test payment in Stripe). After the provider calls your bucket URL:
  1. Open the bucket in the Repost dashboard
  2. Click History to see the incoming event
  3. Click the event row to inspect the request headers, body, and delivery status
You should see the event arrive in history and a successful delivery to your forwarder.

​
What to do next

Bucket modes

Understand the difference between Queue and Proxy mode and when to use each.

Forwarder configuration

Tune retries, timeouts, rate limits, and circuit breaker behavior.

Local development

Use the CLI to forward real webhook traffic to your local machine.

Search history

Filter events by method, path, payload field, status, or time range.