outfit.createdBuyer-initiatedOutfit saved
A buyer committed an outfit in The Atelier — either composed by Ase or self-curated.
When this fires
Fires whenever the underlying state change happens on the platform.
High frequency
This event is buyer-initiated, which means it can fire at checkout-traffic volume during busy periods. Make sure your handler responds in under ten seconds; queue any heavy work.
Sample payload
This is the exact envelope shape we POST to your endpoint — outer wrapper plus the per-event data payload. Field values are randomised on each render so you see the general shape, not a fixed example.
json
{
"id": "86dd176c-0e1d-49b4-bb1f-598ddb06a967",
"event": "outfit.created",
"created": "2026-10-13T20:18:56.811Z",
"data": {
"outfitId": "ck7lc70vw4te0000000000000",
"buyerProfileId": "cghw0a1ykh6o0000000000000",
"title": "Owambe night, gold edges",
"occasion": "owambe",
"itemCount": 4
}
}Use cases
- Trigger any downstream automation that cares about this state change.
- Mirror the event into your data warehouse for analytics.
- Notify a human channel for high-signal events.
Subscribe in the dashboard
To start receiving this event, add it to a webhook's subscription list in Developers → Webhooks. Wildcard subscriptions ( outfit.*) work too — see the webhooks guide for the matching rules.