Delete Customer Data

curl -X DELETE "https://api.genlook.app/tryon/v1/customers/your-user-id" \
  -H "x-api-key: gk_your_api_key"

await fetch(
  `https://api.genlook.app/tryon/v1/customers/${encodeURIComponent(externalUserId)}`,
  { method: "DELETE", headers: { "x-api-key": API_KEY } },
);

import requests

requests.delete(
    f"https://api.genlook.app/tryon/v1/customers/{external_user_id}",
    headers={"x-api-key": API_KEY},
).raise_for_status()

import { Genlook } from "@genlook/api";

const client = new Genlook({ apiKey: process.env.GENLOOK_API_KEY! });

// Idempotent: deleting an unknown id still resolves.
await client.customers.delete("your-user-id");

DELETE

tryon

customers

:externalUserId

curl -X DELETE "https://api.genlook.app/tryon/v1/customers/your-user-id" \
  -H "x-api-key: gk_your_api_key"

await fetch(
  `https://api.genlook.app/tryon/v1/customers/${encodeURIComponent(externalUserId)}`,
  { method: "DELETE", headers: { "x-api-key": API_KEY } },
);

import requests

requests.delete(
    f"https://api.genlook.app/tryon/v1/customers/{external_user_id}",
    headers={"x-api-key": API_KEY},
).raise_for_status()

import { Genlook } from "@genlook/api";

const client = new Genlook({ apiKey: process.env.GENLOOK_API_KEY! });

// Idempotent: deleting an unknown id still resolves.
await client.customers.delete("your-user-id");

Use this endpoint to honor GDPR / right-to-erasure requests. For the given externalUserId, the server:

Deletes every person image stored for that user (both standalone uploads via POST /images/upload and the snapshots attached to past generations).
Deletes every generated result image for that user.
Anonymizes the corresponding generation rows: the user reference is set to NULL, so aggregate analytics survive but nothing ties back to the individual.

The call is idempotent: if nothing matches, the endpoint still returns 204 No Content.

Tracking only kicks in when you supply an externalUserId on the original upload or try-on call. Calls made without one are not linked to anyone and therefore can’t be targeted here; they expire on their own via the retention window. If you have older data created with the deprecated customerId field, pass that same value here: it is the same identifier under its old name.

Request

string

required

The opaque user identifier you originally sent as externalUserId on POST /images/upload and/or POST /try-on.

curl -X DELETE "https://api.genlook.app/tryon/v1/customers/your-user-id" \
  -H "x-api-key: gk_your_api_key"

await fetch(
  `https://api.genlook.app/tryon/v1/customers/${encodeURIComponent(externalUserId)}`,
  { method: "DELETE", headers: { "x-api-key": API_KEY } },
);

import requests

requests.delete(
    f"https://api.genlook.app/tryon/v1/customers/{external_user_id}",
    headers={"x-api-key": API_KEY},
).raise_for_status()

import { Genlook } from "@genlook/api";

const client = new Genlook({ apiKey: process.env.GENLOOK_API_KEY! });

// Idempotent: deleting an unknown id still resolves.
await client.customers.delete("your-user-id");

Response

204 No Content on success. No body.

Get Started

Guides

Try-On

Products (optional)

Account

Releases

Request

Response

​Request

​Response

Request

Response