Inventory Hold
3 min
\<font color="#b6c7cb">\</font> topic type concept purpose inventory hold event overview and guidance on when to send the event audience developers implementing inventory reservation or hold workflows applies to integrations evaluating attempts to reserve inventory does not apply to completed 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 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 user chooses a product, checks out, enters details, and submits a request to hold client processes frontend validation to ensure all fields are filled in properly client retrieves account information, ip, and user agent client's backend server calls to determine whether the hold was successful or not consolidates data and returns a score 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 inventory hold fields https //atlas accertify com/public apis/inventory hold fields