EdgeCron API Documentation
Build scheduled webhooks, event-triggered fanout, delivery observability, retries, dead-letter recovery, and subscription-aware usage with signed API requests.
36
public operations
7
API groups
2
languages
Signed request
HMAC-SHA256 over timestamp and payload
POST /v1/events
X-Key-ID: ak_your_key_id
X-Timestamp: 1782873600
X-Signature: <lowercase hex>Endpoint
Trigger
Task Run
Delivery
Retry
Dead Letter
The delivery pipeline in plain language
These are the names used across the API, dashboard, SDKs, logs, and retry tooling.
Endpoint
Where EdgeCron sends the webhook: URL, method, headers, timeout, signing secret, retry policy, and event filters.
Schedule
A cron or one-shot time trigger. It does not send HTTP by itself; it creates task runs when time arrives.
Event
A business trigger such as invoice.paid. Matching endpoints receive task runs after event fanout.
Task Run
One execution instance created by a schedule, event, or direct API call. It is runtime work, not a reusable template.
Delivery Attempt
One outbound HTTP request with status, latency, response body, error summary, and trace identifiers.
Retry Job
Recovery work scheduled from a failed delivery attempt according to backoff and max-attempt rules.