API ReferenceSubscription
Subscription
Read quota, usage, and resource limits for the current application.
Subscription endpoints are read-only customer-facing views over event usage, quota, and resource limits.
Usage and limits
Where it sits in the pipeline
Subscription endpoints expose plan quota, event usage, and resource limits for the current application.
Remember this distinction
Fan-out and retries are not counted as new billable events; billing follows trigger usage.
Examples:
| Scenario | Task Runs / Delivery Attempts | Billed triggers |
|---|---|---|
| Publish one Event that matches three Endpoints | Three Task Runs and at least three Delivery Attempts | 1 |
| One Schedule fire targets two Endpoints and each delivery retries once | Two Task Runs and four Delivery Attempts | 1 |
| One Delivery Attempt exhausts retries and moves to dead letter | Initial attempt plus retry attempts | 1 |
Manual replay and retry behavior follows the current Delivery Retry API contract; do not model fan-out or automatic retries as additional monthly events.
These endpoints are generated from edgecron/docs/openapi.json and follow the shared EdgeCron response envelope.
| Method | Endpoint | Description |
|---|---|---|
| GET | /subscription/quota | Get subscription quota |
| GET | /subscription/usage | Get subscription usage |
| GET | /subscription/resource-limits | Get resource limits |