Forme Fit API
Size recommendations from one portable shopper profile. JSON over HTTPS. The machine-readable spec is at /openapi.json.
Authentication
Send your key as Authorization: Bearer <key>. Create keys under Console → Integration.
pk_live_…publishable keys can be embedded in web pages and apps. They can recommend sizes, manage the shopper's own profile, read size charts and track events. Restrict them to your domains with allowed origins. Once origins are set, requests without anOriginheader (servers, mobile apps) are refused for that key: use a secret key, or a second publishable key without origins, for apps.sk_live_…secret keys are for your servers only: catalog sync and return feedback. Requests that carry a secret key from a browser are rejected.
Errors and limits
Errors use HTTP status codes with a body of {"error":{"code","message","details?"}}. Each key may make 600 requests per minute; the remaining budget is in X-RateLimit-Remaining.
{ "error": { "code": "product_not_found", "message": "No product with SKU X. Sync it with PUT /v1/products/{sku}." } }
Typical integration
- Your server syncs products:
POST /v1/products/bulknightly, orPUT /v1/products/{sku}on change. - The storefront loads
widget.jswith a publishable key, or calls/v1/profilesand/v1/recommendfrom your own UI. - Track
add_to_cartandpurchasewith therec_idyou received. - Your returns system posts outcomes to
/v1/feedback. Forme recalibrates products that run small or large.
Endpoints
Forme API · Made by Maverick Technologies