Data
Two streams of data, the formats we read each in, the two ways we take them in, and how onboarding works.
Two streams
Swan ingests two streams of data: public data, which is the catalog of what you sell, and production data, which is what your design and pattern teams produce.
| Name | Description | Formats |
|---|
| Public |
| Catalog | What you sell. Titles, sizes, prices, images, availability. | Stripe agentic commerce feed, Google Merchant feed, Shopify export, JSON, CSV |
| Production |
| Fit model measurements | The body the garment was designed for. | PDF, CSV, Excel |
| Tech packs | Flat drawings, garment measurements per size, grading rules, materials. | PDF, CSV, Excel |
| BOMs | What the garment is physically made of. | Excel, Google Sheets, CSV |
| 3D files | Garment data from CLO, Browzwear, or similar. Not required. | GLB, GLTF, native CLO/Browzwear |
Any of these can be sent in batch as JSON, provided each item has a stable identifier.
Delivery
However your data lives today, we can take it in. Either you share it with us, or we pull it from your systems.
Storage drops
You share folders or buckets through one of:
- Google Drive
- SharePoint
- OneDrive
- Dropbox
- S3
Connector integration
We connect directly to your existing systems. Field mapping during setup, scheduled pulls. We build connectors for:
- PLM (product lifecycle management)
- PIM (product information management)
- DAM (digital asset management)
- E-commerce platforms
Onboarding
Onboarding happens with our team in the dashboard. We parse, structure, and version what arrives, agree on measurement definitions with your design team, and fill gaps as we go. Most brands reach a usable state within a few weeks.
Architecture
Swan integrates in three layers: your frontend, your backend, and the Swan dashboard. Your frontend redirects shoppers to capture a Muse. Your backend calls Swan to generate Discovery. Your team works in the dashboard.
Capture
The shopper captures their Muse in Swan's hosted flow, with your branding.
- Your site redirects the shopper to Swan, the shopper captures their Muse on their phone, and Swan redirects them back with a
muse_id. Identity federates with your auth (OIDC, SAML). - You embed Swan's UI components directly and style it to match your theme. Securely interact with Swan using session tokens. Get a pre-built experience for capturing muse.
Discovery
Your backend calls Swan to generate try-on images and a recommended size referencing the user and product context. Get back a try-on image set and a recommended size, which you surface in your existing UI.
Webhooks
Swan notifies your backend when long-running operations complete. Events include scan.failed, scan.measured, muse.completed, muse.failed, tryon.completed and tryon.failed. Each is a signed POST to a URL you configure. Verify the signature with your shared secret before processing.
Rate limits
1000 requests per minute per API key, with a 100-request-per-second burst. A 429 Too Many Requests response means you've exceeded the limit. Higher limits are available on request.
