---
title: Inventory Hold
slug: public-apis/inventory-hold
createdAt: 2026-03-11T19:07:27.585Z
---

::::ExpandableHeading
###

**Topic type: Concept**

:::hint{type="warning"}
**Purpose:&#x20;**&#x49;nventory Hold event overview and guidance on when to send the event.&#x20;

**Audience:** Developers implementing inventory reservation or hold workflows.&#x20;

**Applies to:&#x20;**&#x41;ccount Protection integrations evaluating attempts to reserve inventory.&#x20;

**Does not apply to:&#x20;**&#x43;ompleted purchases, payment processing, or account creation events.
:::
::::

The `inventoryHold` call is intended to inform Accertify when a user attempts to reserve inventory on your website. The aim is to prevent bots from grabbing all available inventory.

### Timing

The API call should come to the Interceptas Platform:

- After a user submits a request to hold an item.
- After they pass error handling, and you retrieve their account details, IP Address, and User Agent.
- Before you send the result of their request.

### Flow

![Inventory Hold flow diagram](https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/qm_EHALBWkIWWs4giA07_-20260318-154722.jpg "Inventory Hold flow")

1. User chooses a product, checks out, enters details, and submits a request to hold.
2. Client processes frontend validation to ensure all fields are filled in properly.
3. Client retrieves account information, IP, and user agent.
4. Client's backend server calls Accertify to determine whether the hold was successful or not.
5. Accertify consolidates data and returns a score.
6. Client determines to allow or deny the hold and moves on with their process, which may involve a purchase or a timed hold.



***

**See also**:

::::LinkArray{contentSource="CUSTOM"}
:::LinkArrayItem{headerType="IMAGE" headerImage="https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/4VRPIgGNjk81XwCl3Q2ea-20260326-200545.png"}
[Inventory Hold Fields](docId\:qwW76R-5x9nMLnrk06Bg8)
:::
::::

