Applications
An application is a logical container within Hook0 that groups related event types, subscriptions, and events. Applications represent your services or products that emit webhook events.
Key Points
- Applications belong to an Organization
- Each application has its own event types, subscriptions, and secrets
- Applications provide usage quotas and consumption tracking
- Deleting an application cancels all pending webhook deliveries
Relationship to Other Concepts
Organization
|
+-- Application
|
+-- Event Types (categories of events)
+-- Subscriptions (webhook endpoints)
+-- Application Secrets (signing keys)
+-- Events (notifications sent)
Applications act as the boundary between your services. A typical setup might have:
- Order Service Application - Emits
order.created,order.shippedevents - User Service Application - Emits
user.registered,user.updatedevents - Billing Service Application - Emits
invoice.paid,subscription.renewedevents
Quotas and Limits
Each application operates within quotas defined by your organization's plan:
- Events per day - Maximum events that can be sent daily
- Event retention - How long events are stored for replay
When quotas are exceeded, new events are rejected until the next billing period.
Onboarding Progress
Hook0 tracks application setup through onboarding steps:
- Event Type - Define at least one event type
- Subscription - Configure at least one webhook endpoint
- Event - Send your first event
Lifecycle
When an application is deleted:
- The application is soft-deleted (can be audited)
- All pending webhook deliveries are cancelled
- No new events can be sent
- Existing subscriptions stop receiving webhooks
Irreversible Action
Deleting an application cannot be undone. All pending webhook deliveries will be cancelled immediately.
What's Next?
- Organizations - Managing the parent container
- Event Types - Categorizing your events
- Application Secrets - Securing webhook signatures
- Events - Sending notifications
- Getting Started - Create your first application