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

# Outbound Webhooks (Planned)

> Current availability and integration guidance for outbound merchant events.

<Warning>
  Crave does not currently offer a public outbound webhook subscription service. There is no
  merchant endpoint configuration screen, external event catalog, signing-secret flow, delivery log,
  retry contract, or production support commitment to integrate against yet.
</Warning>

## Current boundary

Crave receives inbound provider webhooks from services such as Stripe, Square, and DoorDash. Those
provider callbacks are private Crave infrastructure and are not an outbound developer event API.

The repository contains persistence foundations for future outbound delivery, but the endpoint
registry, event producers, delivery worker, signing contract, operator UI, and external acceptance
evidence are not complete. Older examples that referenced events such as `order.created` or
`cart.abandoned`, the `X-Crave-Signature` header, fixed retry delays, or a **Settings > Webhooks**
screen are not implemented contracts and must not be used for production integrations.

## What to use today

* Use the Storefront API and SDK order-result resources for guest checkout outcomes.
* Use private, server-side management API keys only for the documented scoped routes.
* Use provider-specific integration guides only for the inbound provider configuration they
  explicitly describe.
* Coordinate polling, reconciliation, or brand-specific event requirements with your Crave
  integration owner before depending on them.

## Planned contract

The outbound webhook contract will be published only after its endpoint lifecycle, versioned event
schemas, signature and replay policy, retry and deduplication behavior, tenant isolation, delivery
observability, and sandbox conformance tests are implemented. Event names and headers remain subject
to change until that release.

<CardGroup cols={2}>
  <Card title="REST API Essentials" icon="braces" href="/getting-started/rest-api">
    Review the currently supported public and private request boundaries.
  </Card>

  <Card title="Testing" icon="flask-conical" href="/guides/testing">
    Validate the API behavior that is available today.
  </Card>
</CardGroup>