Every event, routed to the right place.

Send orders, alerts and job results to one API. Doqet filters, groups and delivers them to your team's tools.

POST /v1/ingest/src_orders202 Accepted

{
  "type": "order.paid",
  "title": "Order 8841 paid",
  "priority": "high",
  "data": { "amount": 299, "currency": "USD" }
}

type equals order.paid

From event to notification in three parts

Set them up once in the console. After that, your systems only need to send events.

Sources
Give each app, server or script its own HTTPS endpoint and token, then send events with a single POST.
Rules
Match on type, priority, labels or any field in your data. Drop duplicates, group bursts into one message, or hold a send for later.
Destinations
Deliver to your own webhooks, team chat or the workspace inbox. Each destination succeeds or retries on its own.

There is no fixed list of categories. You name the event and choose what happens next.

Connect a destination once, then point as many rules at it as you need.

Doqet answers 202 only after the event is committed. From there, delivery is tracked per destination, attempt by attempt.

Persist before acknowledge: A 202 response means the event and its routing are committed to the database.
At-least-once delivery: A notification can arrive twice, so each request carries a stable delivery ID your receiver can check.
Automatic retries with backoff: Timeouts, network errors, 429s and 5xx responses retry with backoff until they succeed, run out of attempts or expire.
Idempotent ingestion: Send an Idempotency-Key and a repeat within 24 hours returns the original event instead of a new one.
HMAC signatures: Set a signing secret and each webhook carries an HMAC-SHA256 signature over its timestamp, delivery ID and raw body.

See what each plan includes and cancel any time.