Create a custom event to trigger flows with merchant-defined event names and properties.
Custom events allow merchants to trigger flows based on events from their own systems. Events can include custom properties that are accessible in email and SMS templates, and are persisted for segmentation and historical queries.
The API resolves customers using the following priority order:
customer.id — Redo customer ObjectId (highest priority)customer.email — customer email addresscustomer.phoneNumber — customer phone numberAt least one identifier must be provided. If no matching customer is found, one will
be created automatically. If customer.id is provided but not found, the API falls
back to email/phone rather than returning 404.
All datetime values must be formatted as ISO 8601 (RFC 3339) strings, e.g., 2026-04-02T12:00:00Z.
This applies to eventTimestamp, any date-valued properties in data, and any date-valued customFields.
Strings matching this format are automatically detected and indexed as dates for segmentation.
This endpoint is rate-limited to 100 requests per second per store.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Store ID
"64e5a8a1af49a89df37e4ee7"
Custom event to trigger flows with merchant-defined event names and properties.
The name of the custom event (e.g., 'User Registered', 'Loyalty Reward Earned').
Customer identity and profile fields. At least one of id, email, or phoneNumber is required for identity resolution.
Custom properties for this event (must not exceed 400 properties). The size of the event payload must not exceed 5 MB, and each string cannot be larger than 100 KB. For a full list of data limits on event payloads, see Limitations.
Note any top-level property that is not an object can be used to create segments. The $extra property records any non-segmentable values that can be referenced later, e.g., HTML templates are useful on a segment but are not used to create a segment.
ISO 8601 timestamp when the event occurred. Defaults to current time if not provided.
Monetary or conversion value associated with the event (e.g., purchase amount).
ISO 4217 currency code for the value field (e.g., "USD", "EUR").
Merchant-controlled deduplication key (1-255 characters). If provided, subsequent events with the same uniqueId for the same store are silently deduplicated. Use this for safe retries and at-least-once delivery patterns.
Event accepted and queued for processing. No response body is returned.