Make the assets
Try-on needs a digital product before the shopper can open it. There are two doors. Pick the one that matches the files you already have.
Door 1 — shoe photos
Use this when you do not have a 3D file.
| You need | Clear photos of the shoe. Several angles work better. The API has to be able to fetch them over HTTPS if you pass URLs. |
| You connect | POST /api/v1/shoe-3d on api.wearfits.com, the sandbox at tryon.wearfits.com/shoes, or the Shopify / WooCommerce apps, which call the API for you. |
| You receive | A job id immediately, then a GLB and a try-on link when the job finishes. A few minutes is typical. |
| Who skips this door | Shopify merchants. WooCommerce merchants who click Digitize with WEARFITS. |
The call needs a Dashboard API key, except inside the Shopify app, which bills and authenticates inside Shopify. Details: 2D to 3D user guide and API reference.
Shoes only. A bag, backpack, or garment sent here will not become a try-on model.
Door 2 — you already have a 3D file
Use this for shoes when a bureau or a CAD export already produced a model, and for every bag.
| You need | GLB (preferred), GLTF, OBJ, STL, or a zip of OBJ + MTL + textures. Maximum 30 MB. |
| You connect | The library at dev.wearfits.com. Bags and any file that is not a shoe GLB go through that library. The upload call POST /tryon/api/upload_shoe accepts a shoe GLB only. |
| You receive | A product you can open in the viewer at dev.wearfits.com/tryon. |
| Extra step for shoes | Turn on shoe try-on at upload so the shoe is aligned for the camera. |
| Extra step for bags | Position the bag in the editor. Bags are not auto-placed. |
The AR user guide is the click-path for the library. The AR API reference is the upload call.
Where the file goes next
| Goal | Next page |
|---|---|
| Shoe on the foot | See a shoe on the foot |
| Bag on the body | See a bag on the body |
| Garment on a person | Clothing does not use either door. It uses the garment photograph. See a garment. |