Uploading images

A generation requires two publicly reachable image URLs:

Both are required on POST /v1/generations and must be valid URLs. The API does not require either URL to come from DrapeItOn hosting.

Presigned upload (POST /v1/uploads/presigned)

Use this when you need the platform to host image bytes and give you a stable public_url.

Contract (enforced by the API):

1. POST /v1/uploads/presigned with JSON body { "content_type": "…" }.
2. Allowed content_type values: image/png, image/jpeg, image/jpg, image/webp.
3. Response includes:
   • upload_url — perform an HTTP PUT of the raw file bytes here
   • public_url — use this URL later as person_image_url or garment_image_url
4. The PUT must use the same Content-Type you requested.

There is no separate “person” vs “garment” upload endpoint. The same presign + PUT flow produces a public URL you may assign to either generation field.

Example

# 1) Request URLs
RESP=$(curl -sS -X POST "https://api.drapeiton.com/v1/uploads/presigned" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"content_type":"image/jpeg"}')

UPLOAD_URL=$(echo "$RESP" | jq -r .upload_url)
PUBLIC_URL=$(echo "$RESP" | jq -r .public_url)

# 2) Upload bytes
curl -sS -X PUT "$UPLOAD_URL" \
  -H "Content-Type: image/jpeg" \
  --data-binary @./person.jpg

# 3) Use $PUBLIC_URL as person_image_url (or garment_image_url) on submit

When to use which source

Limits

Supported MIME types for presign are listed above. Keep images reasonably sized for e-commerce use; use formats the presign endpoint accepts.

Related

• Quickstart
• Submitting generations
• API Reference — Uploads