> For the complete documentation index, see [llms.txt](https://docs.inqud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inqud.com/crypto-widget/integration/web-hooks/request-web-hook.md).

# Request Web Hook

{% hint style="info" %}
The Request Webhook is required for [API Only](/crypto-widget/overview/api-acquiring-overview.md) integrations. For those utilizing [Inqud Hosted](/crypto-widget/overview/inqud-hosted-page-overview.md) or [Embedded Widget](/crypto-widget/overview/embedded-widget-overview.md) options, please visit [Checkout Web Hook](/crypto-widget/integration/web-hooks/checkout-web-hook.md) page.
{% endhint %}

{% hint style="info" %}
For foundational information on webhooks, including key concepts and verification methods, please refer to the [Webhook Basics](/developer/web-hooks.md) page.
{% endhint %}

Request Web Hooks enable merchant systems to receive timely notifications regarding status changes of Checkouts.

Learn more about requests:

{% content-ref url="/pages/rIaXWS1z1HzF5Bm9ysnl" %}
[Requests](/crypto-widget/explore/requests.md)
{% endcontent-ref %}

### Prerequisites

* Your business account with Inqud is set up.
* The Crypto Widget has been established and configured within the Inqud platform.
* The Crypto Widget is active.

### Setting up Web Hook

* Open the [app](https://app.inqud.com/) and sign in.
* From the left menu bar, choose "Crypto widgets".
* Select the desired widget.
* Open "Webhooks"
* Locate the "Request webhook" option and click on "Add".
* Enter the required details:
  * Webhook link: Provide the URL of your webserver that will handle the callbacks.
  * Webhook secret: Enter a secret key for signature calculation (optional).
* Click on "Save" to finalize your settings.

### Request statuses

<figure><img src="/files/GZprmInfG7eNrNZ8g5e3" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Visit the [Requests page](/crypto-widget/explore/requests.md#request-statuses) to learn more about the various request statuses.
{% endhint %}

### Notification

The Request Web Hook activates with every transition in request status. It requires your web server to respond with a 200 status code. If a different status code is returned, the Web Hook will attempt retries multiple times, using an exponential back-off strategy.&#x20;

For detailed request specifications, please refer to the following page:

[Request Web Hook Specification](https://apireference.inqud.com/#tag/crypto-acquiring-webhooks/operation/user_crypto-acquiring_create-request-webhook) (see **Callbacks** sections)