API ReferenceManagementFlow Management
POST
/v1/mgmt/theme/tenant/{tenantId}

Authorization

Descope Project ID and Management Key
AuthorizationBearer <token>

Project ID:Management Key as bearer token.

In: header

Path Parameters

tenantId*string

Request Body

application/json

styles?object

The tenant's styles, in the same shape the project theme export and import use: an object keyed by style flavor, such as "light" and "dark" for the default style and "-light" and "-dark" for a named one. Every flavor must be an object. The document replaces the tenant's stored styles whole. A logo must be supplied as a base64 data URI, the same way the project theme import takes it. It is uploaded to this tenant's own CDN object, and a read hands it back as a data URI again, so a response can be sent back as a request unchanged. A logo given as a url is rejected, because a url points at an object this tenant does not own.

componentsVersion?string

Read-only: the flow-components bundle version the tenant's styles render against, resolved from the project. Accepted and ignored on write, so a response can be sent back unchanged.

Create or replace the styles a tenant overrides the project theme with, using a valid management key. The styles document replaces the tenant's stored one whole, and the stored theme is returned. A logo must be given as a base64 data URI; it is published to this tenant's own CDN object and never overwrites the project's or another tenant's.

curl -X POST "https://api.descope.com/v1/mgmt/theme/tenant/string" \  -H "Content-Type: application/json" \  -d '{}'
{  "styles": {},  "componentsVersion": "string"}
export interface Response {/** * The tenant's styles, in the same shape the project theme export and import use: an object *  keyed by style flavor, such as "light" and "dark" for the default style and "<styleId>-light" *  and "<styleId>-dark" for a named one. Every flavor must be an object. The document replaces *  the tenant's stored styles whole. *  A logo must be supplied as a base64 data URI, the same way the project theme import takes it. *  It is uploaded to this tenant's own CDN object, and a read hands it back as a data URI again, *  so a response can be sent back as a request unchanged. A logo given as a url is rejected, *  because a url points at an object this tenant does not own. */styles?: {}/** * Read-only: the flow-components bundle version the tenant's styles render against, resolved *  from the project. Accepted and ignored on write, so a response can be sent back unchanged. */componentsVersion?: string}
Was this helpful?