Skip to navigation

Create a catalogue Look

Creates an unpublished look with revision 1 as a draft: an ordered list of applications, each either a variant entry naming one of your variants, a revision of it and one of its application_ids, or a custom entry naming a makeup category with its colour and options. The revision is compiled when it is written: a variant entry pins the variant revision it names, which must be approved, and a custom entry pins the category’s current profile (id, version, digest). An entry that does not compile is 400 INVALID_REQUEST naming applications[i]. Nothing renders a look until a revision is approved and published. Send an Idempotency-Key: a retry with the same key and the same request answers the first response, byte for byte, with Idempotency-Replayed: true, so a response you did not receive is safe to retry. Requires the catalogue.write scope, which your account operator provisions; no other catalogue scope implies it. Served only where the catalogue is enabled for your environment.

Authentication

X-API-Keystring

API key for one environment of your account. Keep server-side; never expose in browser clients.

Headers

Idempotency-Keystring or nullOptional

Request

A new look, unpublished, with revision 1 a draft.
applicationslist of objectsRequired

Response

The look, unpublished, with revision 1 a draft
active_revisioninteger or null>=1
availabilityenum
Allowed values:
created_atdatetime
generationinteger>=1
idstring
latest_revisioninteger>=1
updated_atdatetime

Errors

400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error
409
Conflict Error
503
Service Unavailable Error