Skip to content

Introduction

Revieve is a beauty-tech platform whose core capability is turning user images into structured, actionable data about skin, hair, and makeup — and then mapping that data onto your product catalog.

This site documents the two APIs that surface that capability:

  • Skin Analysis API — a server-side computer-vision endpoint that accepts a JPEG and returns per-metric scores, regional measurements, masks, categorical findings, and quality diagnostics.
  • Product Recommendations API — a catalog-aware service that consumes analysis output (and optionally explicit user preferences) and returns ranked product picks for a given partner taxonomy.

The docs assume you are one of:

  • A partner engineer integrating Revieve into a brand or retailer’s web or mobile app.
  • An internal team building Revieve-powered consumer experiences (concierge, regimen builders, in-store kiosks).
  • An AI coding agent acting on behalf of one of the above. (See the AI agents page for a structured ingestion route.)

A clean integration usually has three layers:

  1. Capture — a camera/upload UI that produces a face-forward JPEG of at least 600×600 pixels.
  2. Analyze — a single POST to the Skin Analysis API with the components your experience needs.
  3. Apply — render results back to the user (visualization overlays, shade picks, product cards), optionally piped into Product Recommendations.

The Your first skin analysis walk-through covers this end-to-end in about ten minutes.

  • Onboarding and Partner ID provisioning. Reach out to your Revieve account contact. The test ID jmlv6b2qtS works against partner-test.revieve.com for evaluation.
  • Revieve Virtual Try-On — the real-time webcam-based try-on product. See the VTO overview and the product page on revieve.com; integration is sales-led.
  • The hosted concierge front-ends (AI Skincare, Makeup, Haircare Advisors; AI Hair Color Artist) — products built on top of the APIs and the VTO engine.
  • Internal-only model components. Some attributes are computed server-side but intentionally not exposed in the public spec.

The Skin Analysis API is server-side: the user’s image is uploaded to Revieve for analysis, processed, and the response is returned.

For real-time experiences (lipstick, eyeshadow, hair-colour try-on), use Revieve VTO instead — it runs in the browser on the user’s own device because face tracking at video frame rate isn’t feasible over a network hop. Webcam frames are not transmitted to Revieve during normal VTO operation, which can be a meaningful posture difference depending on the deployment.

Compliance and data-handling specifics for your deployment are governed by your Revieve agreement.

The Skin Analysis API uses a single base path and identifies itself by spec version (currently 3.x). Backwards-incompatible changes are rare, signposted in the Changelog, and accompanied by a migration guide. New components are additive.