sale accepted v1

wbhk

sale.accepted.v1

Emitted when an accepted-first lifecycle sale has been accepted by the receiver. Carries the full sale payload at the moment of acceptance — the sale status is implied by the event name and is not included in the payload. Listen for this event when you need to act on sale acceptance. To track other lifecycle transitions, see sale.status.updated.v1. Beta feature: this event is in closed beta — request access by emailing [email protected].

Payload

Emitted when a created sale has been accepted by the receiver.

orgId

string

required

^org\d+$

Org ID in standard format

brandId

string

required

length ≥ 1

Brand ID string. Most brands use the format br (e.g. br123). Legacy brands may use the fd format (e.g. fd123) or a plain alphanumeric slug (e.g. mexicancafe). No format is enforced — any non-empty string is accepted.

propertyId

string

required

^p\d+$

Property ID in standard format

salesChannelId

string

required

length ≥ 1

Sales channel ID string. Most sales channels use the format sc (e.g. sc123). Legacy sales channels may be a plain integer without the sc prefix (e.g. 123). No format is enforced — any non-empty string is accepted.

salesChannelType

string

enum

required

Identifies the platform that originated the sale (e.g. UberEats, FlipdishKIOSK, POS).

saleId

string

required

Flipdish sale identifier (Crockford base32 encoding of a global counter, e.g. 3N356).

externalId

string

Partner/platform's own identifier for the sale, when supplied (e.g. an UberEats order ID).

sale

object

required

Full sale payload at the moment of acceptance. The sale status is implied by the event name (always SALE_ACCEPTED) — it is not included as a field in this payload.

Response

200

Your server must return a 2xx to acknowledge