Do I need a separate endpoint for each webhook provider?

Not necessarily.

A good pattern is:

• One webhook endpoint per provider if the provider has unique verification/signature rules, payload shapes, or delivery requirements.
• One shared endpoint if you can reliably distinguish providers by headers, URL path, or secret/signature format and route internally.

Common options

1) Separate endpoints

Example:

• /webhooks/stripe
• /webhooks/github
• /webhooks/slack

Pros

• Simpler verification logic
• Easier debugging and logging
• Cleaner provider-specific handling

Cons

• More endpoints to maintain

2) Single endpoint with routing

Example:

• /webhooks/:provider

Then inspect:

• request headers
• signature scheme
• event type
• secret used

Pros

• Less surface area
• Centralized ingestion

Cons

• More complex code
• Easier to make mistakes with validation/dispatch

Recommendation

If you’re starting out, use separate endpoints per provider unless you have a strong reason to unify them. It keeps signature verification and parsing safer and clearer.

Important

Regardless of endpoint structure:

• verify the webhook signature before processing
• make handlers idempotent
• respond quickly with 2xx
• queue heavy work asynchronously

If you want, I can show a simple routing pattern for multiple providers in Express, FastAPI, or Next.js.