Skip to main content
GET
Get the portal configuration (branding, portals, brands, pages)

Authorizations

Authorization
string
header
required

Supabase JWT — Authorization: Bearer <token>.

Query Parameters

merchant_id
string<uuid>

Optional merchant to scope to. Admins and sub-merchant operators only; other callers always use their token's merchant.

Example:

"28106cba-1c27-4e53-b149-32113e5e8e31"

sections
string

Comma-separated sections to return (default: all): branding, interview-portal, coaching-portal, interview-pages, coaching-pages, brands. A portal the company does not use is left out of the default; name its sections to read them anyway.

Example:

"branding,interview-pages"

Response

The current configuration documents.

merchant_id
string
required

Merchant the configuration belongs to.

Example:

"28106cba-1c27-4e53-b149-32113e5e8e31"

documents
object[]
required

One document per section, each a valid input for portal-configuration-update: kind: "branding", kind: "interview-portal", kind: "coaching-portal", one format: "jobmojito.portal-site" per portal (portal: "interview" for interview-pages, "consumer" for coaching-pages) with every page's DRAFT content and the theme CSS draft, and kind: "brands" when the company's brands are switched on. With style settings switched on, a site document also holds style_settings and css_files (each file with the version to send back), and a page of a sub-brand holds brand. Pages also carry published_at (read-only, ignored on import; null = never published). The support / application-tracking / interview-completed / signed-in home texts are built-in pages ("_support", "_tracking", "_completion", "_signed_in_home") and appear only in the portal-site documents.

block_types
object[]

With page documents (interview-pages, coaching-pages): every block type a page can hold, what it is for and its fields, in the order the editor offers them. Choose blocks from this list.