> ## Documentation Index
> Fetch the complete documentation index at: https://docs.praeto.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Praeto Dispatcher documentation for reliable webhook delivery.

# Praeto Dispatcher

Praeto Dispatcher is the webhook delivery product under the **Praeto Managed Technical Services** brand.

It is built for SaaS teams that need to publish customer-facing webhooks without rebuilding the same reliability layer over and over: queues, retries, dead-letter handling, replay, HMAC signing, idempotency, endpoint health, rate limits, usage tracking, and operational visibility.

## What Praeto Dispatcher does

Your application publishes one event to Praeto Dispatcher. Praeto stores the event, matches it against subscribed endpoint destinations, creates delivery records, queues delivery work, signs outbound requests, retries eligible failures, records attempts, and exposes observability endpoints for debugging and customer support.

```mermaid theme={null}
flowchart LR
  A[Your application] -->|POST /v1/events| B[Praeto Dispatcher]
  B --> C[(Event record)]
  B --> D[Subscribed endpoints]
  D --> E[Queue]
  E --> F[Signed webhook delivery]
  F --> G[Customer endpoint]
  F --> H[(Delivery attempts)]
  H --> I[Replay / DLQ / Metrics]
```

## Current production capabilities

Praeto Dispatcher currently supports:

* Tenant-scoped API keys
* Event publishing with idempotency keys
* Endpoint subscriptions
* Durable delivery records
* Delivery attempts and response capture
* Retry handling for transient failures
* Dead-letter queue listing
* Delivery replay
* Endpoint health metrics
* Metrics summary
* Usage tracking and limits
* Retention cleanup
* HMAC signed outbound webhooks
* Signing secret rotation with overlap
* SSRF protection for endpoint URLs
* DB-backed rate limits
* Payload, endpoint, and fan-out safety limits

## Base URLs

Use the production hostname once your domain is configured:

```text theme={null}
https://api.praeto.dev
```

During development, your Worker URL may look like:

```text theme={null}
https://api.praeto.dev
```

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Publish an event, create an endpoint, and inspect delivery behavior.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/overview">
    Route-by-route details for events, endpoints, deliveries, usage, and admin APIs.
  </Card>

  <Card title="Signature Verification" icon="shield" href="/guides/signature-verification">
    Verify that inbound webhook requests came from Praeto Dispatcher.
  </Card>

  <Card title="Testing" icon="flask" href="/guides/testing">
    Run the PowerShell test suite against a deployed Worker.
  </Card>
</CardGroup>