Create a portal
Create a new help center site on the account. This is the first step of building one entirely through the API: create the portal, allow the locales you need, create categories, then create articles.
The portal is created already reachable by visitors, but empty: only published articles are ever served and articles start as drafts, so nothing leaks while you fill it in. Its allowed_locales starts as exactly the default_locale you send, which matters immediately — a category can only exist in an allowed locale, so a second language needs an update first.
Requires being an administrator of the account.
Authorizations
The id_token from POST /auth/v1/signin, sent as Authorization: Bearer <id_token>. Not the access_token — that one does not carry the identity Cloud Chat authorizes on.
Headers
Your Cloud Chat instance ID — an integer, fixed for your company, told at onboarding. The API overview explains how instances work, how to find yours, and the errors a wrong or missing value produces.
1
Path Parameters
Your Cloud Chat account. It has to be an account your token grants membership on, and it has to live on the instance in the cloudchat-instance header — the two travel together. Account numbers are only unique within an instance, so the same number is a different company on another instance. Usually a mismatched pair fails closed with a 401, because your user does not exist on the other instance — but if your identity happens to exist on both, the call succeeds against the other company's data, silently. Read it and you are looking at the wrong help center; write it and you have stored into the wrong account. Send the two values that were given to you together, and never try a number to see what answers.
1
Body
The portal goes under a portal wrapper. The contract is deliberately small — a logo, more locales and a custom domain are set afterwards, the first two by updating the portal and the last one only in the dashboard.
Response
The portal as stored.
A help center site of the account.
Numeric id, informational only — every help center endpoint addresses the portal by slug.
3
What goes in the portalSlug path segment of the other help center endpoints.
"acme-help"
Display name of the help center.
"Acme Help Center"
Locale used when nothing more specific applies — including as the translation target for an article without a category.
"en"
Locales the portal can hold content in. A category (and through it, an article) must live in one of these.
An archived portal is no longer served to visitors.
false
"2026-05-02T11:04:17.000Z"
"2026-08-10T14:32:05.123Z"