# WEARFITS Virtual Try-On API

> AI-powered virtual try-on, digital twin, and 3D product generation API for fashion commerce.

Last updated: 2026-10-22.

WEARFITS provides API endpoints for:

- Virtual fitting: POST /api/v1/virtual-fitting always creates or reuses a digital twin. Garment slots support outfits with optional shoes; productImage supports a single product, including footwear.
- Photo try-on: POST /api/v1/tryon/clothing and /api/v1/tryon/shoes use personImages or an existing digitalTwinId image without generating a new twin.
- Digital twins: POST /api/v1/digital-twin requires faceImage plus exactly one of bodyPhotoUrl, silhouetteImage, clothingSize, or bodyMeasurements. Inline virtual-fitting uses faceImage + photoUrl for photo mode; photoUrl alone passes current validation but fails uncached generation.
- Estimated size fitting: measurements/clothing-size twins can be compared with merchant body-range size charts; full-body/photo twins do not provide size guidance.
- Shoe and bag 3D generation: convert product images into GLB assets with optional AI texture enhancement and WEARFITS AR upload. Set options.productType to "other" or "auto" for bags.
- Batch digitization: up to 500 products per request, with up to 10 images per product.
- Storefront delivery: use the hosted iframe for the complete try-on plus size-fitting UI, or explicitly choose the lightweight API-backed widget when no hosted size-fitting overlay is needed.

## Primary Links

- Company website: https://wearfits.com/
- Company AI context: https://wearfits.com/llms.txt
- API website: https://api.wearfits.com/
- OpenAPI JSON: https://api.wearfits.com/doc
- Swagger UI: https://api.wearfits.com/reference
- Virtual Try-On API: https://api.wearfits.com/virtual-try-on-api
- Digital Twin API: https://api.wearfits.com/digital-twin-api
- Shoe 3D API: https://api.wearfits.com/shoe-3d-api
- Hosted apparel try-on demo: https://tryon.wearfits.com/demo_tryon.html
- Hosted iframe READY/INIT and base product guide: https://tryon.wearfits.com/docs/integration.html

## Choose an integration path

- Hosted iframe (recommended for storefronts and full size fitting): embed https://tryon.wearfits.com/?sizeFitting=true and follow https://tryon.wearfits.com/docs/integration.html for READY/INIT and base product handoff. Put the optional sizeChart sibling field on each WEARFITS_INIT.payload.products[] item; SET_PRODUCTS uses the same product shape. The chart requires version 1, basis "body", unit "cm" or "in", and body ranges for height, chest, waist, hip, or inseam. The storefront exposes no service API key. Demo: https://tryon.wearfits.com/demo_tryon.html
- Direct API (custom backend and UI): call the documented operations from your backend and implement the customer experience yourself.
- https://api.wearfits.com/widget/tryon.js (lightweight API-backed widget): choose it for a small modal integration. It does not include the hosted iframe's size-fitting overlay.

## Storefront & Product Pages (main site)

This subdomain hosts the developer API. Storefront integrations, AR product
try-on, and marketing pages live on the brand domain wearfits.com:

Live AR viewers and 3D capture use separate platform integrations.
The shoe-3d endpoint generates assets and optionally publishes them to WEARFITS AR.

- Apparel try-on: https://wearfits.com/product/apparel
- Shoe AR try-on: https://wearfits.com/product/shoes
- Bag try-on: https://wearfits.com/product/bags
- Shopify integration: https://wearfits.com/lp2/shopify-shoes/
- WooCommerce integration: https://wearfits.com/lp2/woocommerce-shoes/
- Photo-to-3D digitization: https://wearfits.com/lp2/onboarding/photo-to-3d/

## Agent Documentation

- Full LLM context: https://api.wearfits.com/llms-full.txt
- Virtual try-on markdown: https://api.wearfits.com/docs/virtual-try-on-api.md
- Storefront modal guide: https://api.wearfits.com/docs/shopify-modal.md
- Endpoint summary: https://api.wearfits.com/docs/openapi-summary.md
- Digital twin guide: https://api.wearfits.com/docs/digital-twin.md
- Shoe & bag 3D guide: https://api.wearfits.com/docs/shoe-3d.md
- Product digitization guide: https://api.wearfits.com/docs/digitization.md
- FAQ: https://api.wearfits.com/docs/faq.md
- Glossary: https://api.wearfits.com/glossary
- AI crawler guidance: https://api.wearfits.com/ai.txt

Every landing page also has a clean markdown mirror at <page>.md (e.g.
https://api.wearfits.com/virtual-try-on-api.md), or request a page with `Accept: text/markdown`.

## Integration Skills

Step-by-step integration playbooks for AI agents. JSON index at https://api.wearfits.com/skills; each skill body is markdown.

- API integration (direct HTTP): https://api.wearfits.com/skills/wearfits-api-integration.md
- Embeddable try-on widget: https://api.wearfits.com/skills/wearfits-virtual-tryon-widget.md
- Shopify integration: https://api.wearfits.com/skills/wearfits-shopify-integration.md
- WooCommerce integration: https://api.wearfits.com/skills/wearfits-woocommerce-integration.md

## Core API Endpoints

- POST /api/v1/virtual-fitting
- POST /api/v1/tryon/clothing
- POST /api/v1/tryon/shoes
- POST /api/v1/digital-twin
- GET /api/v1/digital-twin/{id}
- POST /api/v1/size-fitting
- POST /api/v1/shoe-3d
- POST /api/v1/digitization/batches
- GET /api/v1/jobs/{jobId}

## Authentication

Protected direct API operations require X-API-Key when their effective OpenAPI security includes the default apiKey scheme. Check each operation and its overrides at https://api.wearfits.com/doc; public and separately authenticated exceptions declare their own requirements there. Public documentation, /llms.txt, /llms-full.txt, and /widget/tryon.js do not require authentication. The hosted iframe handles API access without exposing a service key in storefront code.

Merchant-key and bare-service-key jobs belong to the submitting key. Account-attributed service jobs and storefront-token jobs use their respective account-scoped ownership. Keep the same authentication mode and ownership when polling; an unrelated owner gets 404. Storefront tokens only allow virtual-fitting submission and job polling. See /llms-full.txt for renewal and callback verification.

## Rate limits

API requests share an additional per-IP 60-second allowance: 6,000 reads, 1,200 writes, 600 uploads, and 3,000 result-file requests. Users behind the same proxy or NAT can share that allowance; counts are approximate by location. A 429 from this early limit includes Retry-After: 60 and X-Request-ID. X-RateLimit-* headers describe endpoint limits when available and may be absent on an early 429 or 503. The plain health check, static documentation and CORS preflight are outside this additional limit.