---
title: Listing Update
slug: public-apis/listing-update
createdAt: 2026-03-11T19:07:57.387Z
---

::::ExpandableHeading
###

**Topic type: Concept**

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

**Audience:** Developers implementing marketplace listing modification flows.&#x20;

**Applies to:&#x20;**&#x41;ccount Protection integrations evaluating updates to existing listings.&#x20;

**Does not apply to:&#x20;**&#x41;ccount creation, authentication events, or initial listing creation.
:::
::::

This is a Marketplace-specific event. This is for clients who allow third-party Producers (sellers) on their website. The `listingUpdate` call is intended to retrieve an Account Protection Score when a Producer attempts to update a listing on your website.

### Timing

The API call should come to the Interceptas Platform:

- After a user submits an update request to a product or service.
- 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

![Listing Update flow diagram](https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/knXJlu3MRJw5l3j3kg_Md-20260318-154722.jpg "Listing Update flow")

1. User arrives on site and logs in.
2. User updates an existing listing to offer a product or service.
3. Client processes frontend validation to ensure all fields are filled in properly.
4. Client retrieves account information, IP, and user agent.
5. Client's backend server calls Accertify.
6. Accertify consolidates data and responds back with a score.
7. Client determines appropriate action for the `listingUpdate`.



***

**See also**:

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

