Dashboard
WebhooksSubscription Bot Webhooks | BotSubscription
Webhooks

Subscription Bot 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: Notifications arrive independently of the checkout response. A completed API request does not confirm that your receiver has received the event.
  • At-Least-Once Delivery: We aim to deliver every event to your server at least once. Transient failures are retried 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:

  • Register endpoints with a publicly reachable HTTPS URL, including during development.
  • Localhost, loopback, private and reserved addresses are blocked. Hostnames are checked at registration and delivery.
  • Redirects are not followed. Configure the final receiver URL and path directly.
  • The system provides a unique signing secret only at creation. Store it immediately; endpoint listings omit it.
  • You can manage your endpoints programmatically via the Webhook API Reference.

API-key access

Restricted project API keys can create endpoints with webhooks:create and delete them with webhooks:delete.

Listing and testing endpoints require an unrestricted project API key. Restricted keys receive 403 FORBIDDEN on those operations, regardless of their scopes.

Next Steps

To build a secure and resilient webhook integration, explore our dedicated guides:

Last updated: