Hooksbase

Glossary · Product

Ingest

Accepting an event into Hooksbase via HTTP, email, form, or scheduled cron.

Product

What is ingest?

Ingest is the first step of the webhook lifecycle in Hooksbase: accepting an event into Hooksbase. Once an event is ingested, it's persisted, queued for delivery, and routed to the selected destination.

Hooksbase supports four ingest channels:

  • HTTP webhooks — POST /v1/ingest/{webhook-id}, authenticated with the webhook's bearer ingest secret
  • Email — each webhook gets a dedicated address hook_<id>@ingest.hooksbase.com
  • HTML forms — POST /v1/form/{webhook-id} accepting multipart and CORS
  • Scheduled cron — Starter+ per-webhook recurring trigger with a configurable static payload template

All four channels normalize to the same internal event shape, so downstream routing, transforms, retries, and observability work identically regardless of how the event arrived.

What happens during ingest

For every ingest:

  1. Authentication — HTTP ingest checks the Hooksbase bearer ingest secret; configured provider signatures are verified after that; for other providers, verify before ingest in a forwarder if you need native provider signature checks
  2. Idempotency check — for HTTP ingest, honor the Idempotency-Key header and refuse duplicates before quota admission
  3. Quota admission — check ingest rate limit; reject with 429 if exceeded
  4. Payload persistence — store the raw bytes for later replay
  5. Delivery scheduling — create a delivery record for the resolved destination

Once these steps complete, Hooksbase responds 2xx to the producer. Actual delivery to your endpoints happens asynchronously.

Why decoupling ingest from delivery matters

The producer (Stripe, your form, your cron) sees a fast 2xx as soon as ingest succeeds. Whether your destination is fast, slow, or temporarily down doesn't affect the producer's experience. Delivery is Hooksbase's problem from that point forward.

For deeper reading: Event infrastructure for AI agents.

Frequently asked questions

What happens during ingest?

Five steps: authentication against the bearer ingest secret and any configured provider signature, an idempotency check on the Idempotency-Key header before quota admission, quota admission that rejects with a 429 if the ingest rate limit is exceeded, persistence of the raw bytes for later replay, and creation of a delivery record for the resolved destination.

Why is ingest decoupled from delivery?

So the producer sees a fast 2xx as soon as the event is accepted, whether your destination is fast, slow, or temporarily down. Delivery becomes Hooksbase's problem from that point forward rather than something the producer waits on.

What is Hooksbase?

Hooksbase is event infrastructure for AI agents. It ingests events over four channels — HTTP, email, HTML form, and scheduled cron — verifies them, routes them by rule, runs versioned Automations in the event path, and delivers them to HTTP and cloud destinations (AWS SQS, AWS EventBridge, GCP Pub/Sub, and S3-compatible storage) with retries, strict ordering, Standard Webhooks-compatible signing, deterministic replay, and a dead-letter path. It is a hosted service, runs on Cloudflare Workers, is operated at hooksbase.com, and is not affiliated with — and shares no code or ownership with — other similarly named webhook, hook, or tunnelling tools.

Related terms

Back to glossary