Do I need to accept webhooks from multiple providers in one endpoint?

Not necessarily. It depends on your architecture and operational needs.

Common options

1) One endpoint per provider

• Example: /webhooks/stripe, /webhooks/github, /webhooks/shopify
• Pros:
  • Simpler routing and validation
  • Easier to isolate failures
  • Cleaner provider-specific logic
• Cons:
  • More endpoints to manage

2) One shared endpoint for multiple providers

• Example: /webhooks/incoming
• Pros:
  • Fewer public endpoints
  • Centralized ingestion/logging
• Cons:
  • You must identify the provider from headers/path/body
  • More complex validation and parsing
  • Harder to keep provider logic clean

Recommendation

If you have only a few providers, use separate endpoints. It’s usually easier and safer.

Use one endpoint only if:

• your platform requires it,
• you want a single gateway layer,
• or you’re normalizing all incoming webhooks before dispatching internally.

Important note

Even if you use one public endpoint, it’s often best to internally route to provider-specific handlers after verifying signature and source.

If you want, I can show a clean design for either:

• one endpoint with provider dispatch, or
• multiple endpoints with shared validation.