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

# Configure endpoints and inspect deliveries

> Register an event destination, understand event and delivery records, and investigate missing or failed notifications.

Webhooks notify your integration about underwriting, monitoring and other subscribed events. Owners and Developers manage destinations in **Dev Tools > Endpoints** and inspect outgoing activity in **Deliveries & events**.

## Register an endpoint

1. Select the correct workspace and environment.
2. Open **Endpoints** and select **Add webhook**.
3. Enter a recognizable name and a public HTTPS hostname on port 443 controlled by your team. Use the final URL; redirects, private addresses and URL credentials are not supported.
4. Select individual event subscriptions, or use **Select all** / **Clear**. Saving requires at least one event. Editing preserves the selected subset. Billing events are available only to Owners. Complete the requested identity confirmation.
5. Store the signing secret securely when it is shown, and implement signature verification in your receiver.

Use the endpoint drawer to inspect or edit its configuration. An endpoint being enabled does not prove that your server has received an event. Confirm delivery with a controlled test.

## Inspect a delivery

Open **Deliveries & events** and filter or search for the event associated with your record. Select a row to inspect the available event payload, destination, status, response and attempt details.

![Deliveries and events table showing seeded webhook activity, event types and delivery statuses.](https://mintcdn.com/amlok-docs/HXjKmnxFg9L3P2cw/images/console/webhook-deliveries.jpg?fit=max\&auto=format\&n=HXjKmnxFg9L3P2cw\&q=85\&s=3dd20a926a0afcbb3b30c7398fda8823)

Use event and delivery records to follow notifications independently of incoming API requests.

Keep these identifiers separate:

| Identifier | Purpose |
| - | - |
| Event ID | Identifies the business event and supports deduplication. |
| Endpoint ID | Identifies the configured destination. |
| Delivery or attempt ID | Identifies an attempt to send the event. |
| Related record ID | Connects the event to an origination, monitored deal or other product record. |

## Troubleshoot missing notifications

* **No event record:** check that the product action completed and that the expected event type applies. A successful submission can still be processing.
* **No matching destination:** check the endpoint's environment, status and event subscriptions.
* **Failed delivery:** inspect the receiver's response, HTTPS availability and signature handling.
* **Repeated event:** deduplicate by event identity and make your handler safe to run again.
* **Out-of-order delivery:** reconcile with the current API record instead of treating arrival order as business order.

Implement signature verification against the original request body, acknowledge promptly and process asynchronously. Follow [webhook operations](https://docs.amlok.io/api-reference/webhook-operations.md) for retry, replay and secret-handling rules, and the [event catalog](https://docs.amlok.io/api-reference/event-catalog.md) for payload meanings. Do not assume opening a delivery in the console replays it.

## Test safely in Sandbox

Sandbox scenarios record example events and deliveries. Outbound test delivery requires the scenario's explicit delivery option and an eligible endpoint you control. The separate demonstration site suppresses outbound delivery; its records illustrate the experience without contacting external systems.

Start with a successful receiver, then test failure, duplicate and retry handling. See [Sandbox scenarios](https://docs.amlok.io/console/sandbox.md) and the [webhook integration guide](https://docs.amlok.io/api-reference/webhooks.md).

## Update and rotate

Choose **Edit endpoint** to change the URL, exact subscriptions or enabled status. Disabling stops future/queued sends once the worker checks the endpoint; a request already in flight can finish. Re-enabling does not backfill events recorded while the endpoint was disabled. Replay retained events explicitly if needed.

Choose **Rotate signing secret** in the endpoint actions. Copy the new secret once and update your receiver within the 24-hour overlap. The drawer displays the previous-secret expiry, retry delays, timeout and replay window. Rotation needs identity confirmation, and a second rotation is blocked during the overlap.

In **Deliveries & events**, a row marked **Recorded** is a business event, not proof of delivery. Attempt rows show the endpoint ID, HTTP result, duration, safe error code and scheduled next attempt when present. `exhausted` means no automatic retry remains. Historical/demo records may have fewer diagnostics. See the [complete error catalog](https://docs.amlok.io/api-reference/errors.md).

Replay is an authenticated API action using `POST /v1/webhook-replays`, an existing event and enabled endpoint ID, and an idempotency key. Use Data Lookup for the request example. Repeating a replay with the same key returns the original receipt; a new key intentionally requests a new delivery. This does not charge for or rerun the original business action.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.