Skip to navigation

Publish a catalogue Look revision

Makes an approved look revision the one new try-ons render, at the expected_generation you read (409 GENERATION_CONFLICT otherwise). A revision that is not approved answers 409 REVISION_NOT_APPROVED; a retired look 409 LOOK_RETIRED. Every dependency the revision pins must still be available: a pinned variant that is retired, or a pinned profile that is withdrawn, answers 400 INVALID_REQUEST with look_dependency_unavailable at applications[i], and nothing moves. Publishing an earlier approved revision is rollback. 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.publish 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.

Path parameters

look_idstringRequired

Headers

Idempotency-Keystring or nullOptional

Request

Make an approved look revision the one new admissions render. Every dependency it pins must be available now: each variant revision approved and its variant not retired, each profile version not withdrawn.

expected_generationintegerRequired
revisionintegerRequired

Response

The look, rendering the published revision
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
404
Not Found Error
409
Conflict Error
503
Service Unavailable Error