Skip to main content
Brand API generates webhook event data to notify your application about brand activity, brand updates, verification changes, and other important changes. Use these event types to keep your backend systems, cached brand data, and application workflows up to date.

​
Brand Events

Brand events are triggered when changes happen to brand objects. These events help your application respond to updates in brand profiles, company information, verification status, ownership claims, or brand availability.

​
brand.updated

  • Namespace: brand
  • Triggered when: A brand’s core data is updated.
Use this event when your application needs to refresh stored brand information, update cached brand assets, or sync the latest brand profile data.

​
brand.company.updated

  • Namespace: brand
  • Triggered when: A brand’s company-level data is updated.
Use this event when your application depends on company metadata such as company details, firmographic data, or business profile information.

​
brand.verified

  • Namespace: brand
  • Triggered when: A brand’s data has been human-reviewed and verified by the Brand API curation team.
Use this event when your application needs to identify trusted, reviewed, or verified brand records.

​
brand.claimed

  • Namespace: brand
  • Triggered when: A brand is officially claimed by its owner.
Use this event when your application needs to track brand ownership status or update trust signals related to a brand profile.

​
brand.deleted

  • Namespace: brand
  • Triggered when: A brand is removed from the Brand API index.
This event is rare and usually happens at the request of the brand owner. Use this event to remove outdated brand records, clear cached assets, or stop showing deleted brand data in your application.

​
Subscribing to Events

You can choose which webhook event types you want to receive when setting up your webhook endpoint. Each webhook event payload includes a type field. Your application can use this field to determine how the event should be processed. For example, your backend can process a brand.updated event differently from a brand.deleted event. Only subscribe to the event types your application needs. This reduces unnecessary traffic, lowers server processing, and keeps your webhook integration easier to maintain.