Storefront widget
The fastest path: let WooChim detect product context, load the SKU chart, and render the shopper flow.
View storefront pathDeveloper hub
Build fit into the store you already own.
Start with one asynchronous script or call the retailer API directly. Keep the catalogue, product page, cart, and checkout under your control.
Hosted widget
HTML<script
src="https://www.woochim.com/woochim-widget.js"
data-key="YOUR_PUBLISHABLE_KEY"
async>
</script> Async load Publishable key No checkout redirect
Two implementation paths
Hosted when useful. Headless when necessary.
Retailer API
Own the interface and call fit, catalog, size-chart, render, and event contracts from your existing stack.
View API overviewRetailer contract map
The endpoints behind the product-page decision.
GET
/api/v1/catalogProducts detected for the connected merchant.
GET
/api/v1/sizes?sku=The exact chart WooChim reads for a product SKU.
POST
/api/v1/fitRecommended size, fit probabilities, confidence, and assumptions.
GET
/api/v1/embed/configPer-store widget configuration and plan-gated presentation.
POST
/api/v1/eventsFirst-party widget and fit usage events.
POST
/api/v1/store/order · returnServer-side order and return outcomes for retailer reporting.
Direct fit request
The image is optional. The fit contract is not.
A fit response returns the recommendation, probabilities, confidence, and assumptions. Missing inputs remain visible rather than becoming false certainty.
Fit request
cURLcurl -X POST https://www.woochim.com/api/v1/fit \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"body": {"chest": 98, "waist": 83, "hips": 96},
"garment": {
"category": "tshirt",
"size": "M",
"chest": 52,
"waist": 50
}
}'Non-negotiable contracts
Small details that prevent big fit errors.
These rules match the production widget and APIs today. They are not aspirational SDK documentation.
Flat garment centimetres
Garment chest, waist, and hip values are half measurements. WooChim doubles them before comparing with body circumference.
Two key scopes
Publishable keys belong in the storefront. Secret keys stay server-side for protected and paid operations.
Honest confidence
Sparse measurements and unknown fabric widen the distribution and appear in the response assumptions.
Bring one real SKU. Leave with a verified implementation path.
Private launch onboarding validates the chart, key scope, product mapping, and live storefront flow before traffic opens.
Join retailer waitlist