Webhooks Overview
Outbound webhooks allow you to connect your custom external applications, websites, databases, or third-party CRM systems with BotSubscription. By listening for real-time HTTP POST notifications, your backend server can react immediately when members subscribe, make payments, or lose access.
If you use a Telegram subscription bot or a Discord subscription bot to manage and monetize your private community, webhooks provide the bridge to synchronize this activity with your own internal infrastructure.
Delivery Model
- Per-Project Isolation: Every webhook endpoint is strictly tied to a single parent project. Your external receiver URL only receives events produced within that specific project, with no cross-project leakage or global fan-out.
- Asynchronous Delivery: Events are enqueued instantly. Our background workers process and push deliveries without blocking the client's checkout or payment transaction flow.
- At-Least-Once Delivery: We aim to deliver every event to your server at least once. If a transient failure occurs (a network blip or a
5xx), the worker retries on a capped backoff schedule — see Deduplication & Retries for the full policy. - Unordered Delivery: Events from independent operations may arrive out of chronological order. We recommend using timestamps to reconcile state.
Registering Webhook Endpoints
You can register, test, and manage your endpoint URLs directly within the Developer section of your BotSubscription dashboard, or programmatically using our developer routes.
When configuring webhooks:
- You define the destination URL that will receive the JSON payloads.
- The system provides a unique signing secret to secure your endpoint.
- You can manage your endpoints programmatically via the Webhook API Reference.
Next Steps
To build a secure and resilient webhook integration, explore our dedicated guides:
- Learn how to secure your receiver in Signature Verification.
- Implement robust processing in Deduplication & Retries.