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": "d0c493b3-eca7-4478-8b24-caf0b2051d0e",
  "event": "outfit.created",
  "created": "2026-10-25T18:11:03.978Z",
  "data": {
    "outfitId": "c5gzttr4mzfc0000000000000",
    "buyerProfileId": "c4jfkx293kae0000000000000",
    "title": "Lagos Fashion Week front row",
    "occasion": "office",
    "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.