mapping.error.resolved fires when a mismatch report transitions to a terminal state — either FIXED (we agreed and corrected the mapping) or REJECTED (we kept the existing mapping). Use it to stop nagging your ops team and to mark the issue closed in your downstream system.
When it fires
On the state transition fromOPEN or IN_PROGRESS to FIXED or REJECTED. Subsequent state changes (e.g., reopening) do not re-fire.
Required plan
Pro and above.Recipients
Only the organization that owns the mismatch report (i.e., the one that originally reported the mismatch).Payload
Fields
| Field | Type | Notes |
|---|---|---|
data.reportId | UUID | The mismatch report that was resolved. |
data.partnerInventoryId | UUID | null | The inventory the reported mapping belongs to. |
data.partnerHotelId | string | null | Your hotel identifier from the inventory. |
data.referenceHotelId | string | null | The reference hotel the mapping was pointing at. |
data.resolution | "FIXED" | "REJECTED" | How the report was closed. |
data.resolvedAt | ISO timestamp | When the report transitioned to its terminal state. |