Endpoints

Create try-on (sync)

The same as Create try-on, except the server holds the request open until the image is ready — up to about 55 seconds — so most of the time one call is all you need.

POSThttps://fabricvton-api.onrender.com/api/v1/tryons/sync

Request

Headers and body are exactly the same as for Create try-on, including the Idempotency-Key.

Headers

Body

Give each image either as a URL or as the id of an image you uploaded — exactly one of the two for the person, and exactly one for the garment. You can mix them: an uploaded shopper photo with a garment URL from your CDN is the most common pairing.

Rules for image URLs

• HTTPS on the default port.
• The URL returns the image itself with HTTP 200. Redirects are not followed.
• It responds within 12 seconds.
• The file is a JPEG or PNG, no larger than 4 MB.

Signed URLs are fine as long as they're still valid when the request arrives. Uploaded images skip these rules entirely, which is one reason to prefer them for shopper photos.

Set a long enough timeout

Give your HTTP client a timeout of at least 70 seconds. Many clients default to 30 seconds, which would cut the connection while the image is still being made. If your connection drops anyway, nothing is lost: the try-on carries on, and repeating the request with the same Idempotency-Key picks it back up without a second charge.

Example

curl -X POST https://fabricvton-api.onrender.com/api/v1/tryons/sync \
  --max-time 75 \
  -H "Authorization: Bearer $CLOTHSY_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "personImageId": "img_5Hq2mV8xKc3TnR7w",
    "garmentImageUrl": "https://your-cdn.example.com/denim-jacket.jpg",
    "title": "Cropped denim jacket",
    "consent": true
  }'

Response

When the try-on finishes within the wait, you get 200 with its final state — the same shape as Get try-on:

{
  "id": "7f3c2a9e-1d4b-4c1e-9a55-2b8f0c6d4e10",
  "status": "success",
  "resultUrl": "https://fabricvton-api.onrender.com/i/eyJ..."
}

{
  "id": "7f3c2a9e-1d4b-4c1e-9a55-2b8f0c6d4e10",
  "status": "failed",
  "resultUrl": null,
  "message": "That try-on did not finish. Your credit has been returned."
}

If it isn't finished when the wait runs out, you get 202 instead — exactly what Create try-on returns. Carry on by polling pollUrl every 2–3 seconds.

{
  "id": "7f3c2a9e-1d4b-4c1e-9a55-2b8f0c6d4e10",
  "status": "pending",
  "pollUrl": "/api/v1/tryons/7f3c2a9e-1d4b-4c1e-9a55-2b8f0c6d4e10"
}

So always handle both: check the HTTP status, and treat 202 as “poll from here”. The SDK's tryons.run() does this for you.

Errors

The same as Create try-on, with the same rate limit of 12 starts a minute per account.