Skip to main content
Fire emits this event when a channel’s configuration changes — name, status, authentication type, or base URL. Your system should update its local channel mapping and re-fetch the channel list if it caches it.

​
Payload

{
  "event": "channel.updated",
  "id": "evt_abc200",
  "created_at": "2025-01-20T15:30:00Z",
  "data": {
    "account": "1",
    "country": "6",
    "vendorId": 16,
    "channel": {
      "channelId": "CH-IFOOD-001",
      "code": "IFOOD",
      "name": "iFood",
      "description": "Orders received via iFood marketplace",
      "active": "ACTIVE",
      "authType": "API_KEY",
      "baseUrl": "https://api.ifood.com.br",
      "createdAt": "2025-01-15T10:00:00.000Z",
      "updatedAt": "2025-01-20T15:30:00.000Z"
    }
  }
}

​
Fields

​
data

FieldTypeDescription
accountstringAccount identifier — required by downstream systems
countrystringCountry identifier — required by downstream systems
vendorIdintegerBrand identifier
channelobjectUpdated channel object — see below

​
data.channel

FieldTypeDescription
channelIdstringUnique channel identifier
codestringShort code for the channel (e.g. IFOOD, RAPPI, KIOSK)
namestringDisplay name
descriptionstring | nullOptional description
activestringChannel status: ACTIVE or INACTIVE
authTypestringAuthentication mechanism: API_KEY, OAUTH2, BASIC_AUTH, XMART_LOGIN, or NONE
baseUrlstring | nullBase URL for the channel’s integration endpoint
createdAtstringISO 8601 creation timestamp
updatedAtstringISO 8601 last-updated timestamp

​
Usage

1

Verify the signature

Validate X-Fire-Signature. See Authentication.
2

Acknowledge immediately

Return 200 OK before processing.
3

Update your channel mapping

Upsert the channel in your local store using channelId as the key. If the channel transitions to INACTIVE, stop routing events or orders to it.