SkinLabs® Platform API

Build South African skin intelligence into your clinic or product. The SkinLabs Platform API gives clinics, retailers and integrators access to SA-specific skin data: UV and humidity by city, independent product reviews scored for local climate, and an ingredient catalogue built for melanin-rich skin and Highveld-to-coastal conditions.

GET https://gnkpzijxuciiaamakgzm.supabase.co/functions/v1/skin-weather?city=johannesburg

{
  "city": "johannesburg",  "cityLabel": "Johannesburg",
  "uvNow": 9.4,  "uvMax": 11.2,  "uvPeakAt": "2026-10-03T10:00:00.000Z",
  "humidity": 28,  "tempMax": 27,
  "fetchedAt": "2026-10-03T08:41:12.000Z",  "stale": false,
  "attribution": "Weather data © OpenWeather"
}

Response values are illustrative; the shape matches the deployed function.

What's ready today, and what isn't

Every endpoint carries one of two labels. Select a label to filter the reference.

Getting started

Base URL

Partners should integrate against the v1 domain once it exists. The current URL exposes the hosting project reference and will change if SkinLabs ever migrates projects.

Authentication

The live skin weather endpoint is public and needs no credentials. Every v1 endpoint will require a partner key sent as a header, issued per organisation so usage can be metered and revoked independently.

X-SkinLabs-Key: sk_partner_live_xxxxxxxxxxxxxxxx

Conventions

Skin weather

curl "https://gnkpzijxuciiaamakgzm.supabase.co/functions/v1/skin-weather?city=cape-town"

const res = await fetch(
  "https://gnkpzijxuciiaamakgzm.supabase.co/functions/v1/skin-weather?city=cape-town"
);
const weather = await res.json();
if (!res.ok) throw new Error(weather.error); // e.g. "unknown_city"
if (weather.stale) console.info("Cached reading from", weather.fetchedAt);

Product reviews

Products and ingredients

Ingredient compatibility

POST /v1/interactions/check
X-SkinLabs-Key: sk_partner_live_…
Content-Type: application/json

{ "ingredients": ["retinol", "glycolic acid", "niacinamide"] }

{
  "resolved": [
    { "input": "retinol",       "slug": "retinol",       "resolved": true },
    { "input": "glycolic acid", "slug": "glycolic-acid", "resolved": true },
    { "input": "niacinamide",   "slug": "niacinamide",   "resolved": true }
  ],
  "conflicts": [
    { "a": "retinol", "b": "glycolic-acid", "severity": "caution",
      "guidance": "Alternate nights rather than layering." }
  ]
}

SKYNN assessments

Partner enquiries

Errors and caching

Every error response is JSON with an error field holding a stable, machine-readable code. Branch on the code, not on the HTTP message text.

{ "error": "unknown_city" }

Caching

Skin weather readings are cached per city on SkinLabs' side and shared by every caller, so partner traffic never multiplies calls to the weather provider. Responses carry Cache-Control: public, max-age=600; cache for up to 10 minutes on your side.

Proposed v1 rate limits

Over the limit, v1 would return 429 with {"error":"rate_limited"} and a Retry-After header in seconds. These limits are a proposal and are not enforced today.

Usage rules

These rules come from obligations SkinLabs already carries. Partners inherit them when they display SkinLabs data.

Before v1 opens

What has to exist before the first partner clinic can use the proposed endpoints. None of this is built yet.

• A single partner gateway on api.skinlabs.co.za that maps v1 paths to read-only queries.
• Partner keys: issued per organisation, stored hashed, checked on every request and revocable.
• Per-key rate limiting by tier.
• A review that the catalogue data exposed through the gateway contains no member, payment or analytics rows.
• A POPIA operator agreement, needed before any clinic sends patient questionnaire data to SKYNN.
• Published partner terms covering attribution, sponsored disclosure, no-diagnosis framing and pricing per tier.
• A sandbox with seeded catalogue data.

Interested in early access? Talk to us about partnerships.