Skip to main content
inventory.duplicate.resolved is the broad fan-out event. When we close a duplicate report on hotel X, every Pro+ organization with at least one active mapping pointing at X is notified, regardless of who originally filed the duplicate. If your downstream system caches the hotel id you mapped to, this is your signal to invalidate that cache.

When it fires

When a ReferenceHotelDuplicateReport is resolved by our team. The same event id may be delivered to many subscriptions (one per receiving org).

Required plan

Pro and above.

Recipients

Every organization with at least one partner_mapping_result whose matchedReferenceHotelId is either the original or the duplicate hotel id.

Payload

Fields

What to do

  • If resolution = FIXED and any of your mappings point to duplicateHotelId, those mappings will be redirected to originalHotelId server-side. You should invalidate any cached reference data and consider re-fetching the mapping result.
  • If resolution = DISMISSED, no mapping changes — but you may still want to record that we explicitly considered and rejected the duplicate.

Example: cache invalidation (Python)