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

# Webhooks

> Receive updates on your server and keep payment status in sync.

Webhooks send updates to your server so your integration can react to account activity. Contact [support@ledig.io](mailto:support@ledig.io) to set up delivery and obtain the event types, payload examples and signature-verification instructions for your integration.

Set up separate receivers or configurations for sandbox and live deliveries. Test delivery and signature verification before relying on events to update payment status.

## Handle deliveries

Your receiver should:

* Verify each delivery using the webhook verification instructions and secret supplied for that environment.
* Use the delivery identifiers to recognise duplicates.
* Handle events that arrive later than expected or out of order.
* Read the resource when you need its current status.

Keep webhook secrets on your server. Do not reuse the API request-signing process for webhook verification, and keep complete event bodies and signing values out of logs.

## Confirm the current status

You can also use these endpoints to keep your integration up to date:

| What you need | Endpoint |
| - | - |
| Transfer progress | `GET /v1/transfers/{id}` |
| Transaction history | `GET /v1/transactions` |
| Available funds | `GET /v1/balances` |
| Crypto address setup | `GET /v1/wallets/network/{requestId}` |
| Bank receiving details | `GET /v1/virtual-accounts/{currency}` |

Leave a delay between status requests and increase it while you wait. Follow `Retry-After` when returned. Use the returned cursors when reading transaction history.

## Environment label

The `x-ledig-environment` header identifies the delivery environment:

| Value | Environment |
| - | - |
| `sandbox` | Sandbox |
| `live` | Live |

Retries keep the same label. A replay of an older event may not include it.

Use the label to help distinguish deliveries in your integration. It is not covered by the event signature and must not replace signature verification or your receiver's environment configuration.


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