Sign in
Events/Atelier
outfit.createdBuyer-initiated

Outfit 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": "e3fbb263-babb-4bde-9918-efc8ead5b18c",
  "event": "outfit.created",
  "created": "2026-10-28T01:11:00.585Z",
  "data": {
    "outfitId": "c80xdg985rkr0000000000000",
    "buyerProfileId": "cbo1hpwv9lpa0000000000000",
    "title": "Lagos Fashion Week front row",
    "occasion": "date",
    "itemCount": 5
  }
}

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.