Languages

Update a language list

Changes the fields sent: mainLanguageName, or the whole languages array (send every language you keep). Live at once, with the same checks as the Languages screen: a new language gets its home page and its own addresses (/fr/…), a removed one keeps its translations for when its code comes back. A code that isn’t a language code, that is en, that a page’s address already starts with, or that is one of the site’s own addresses is refused with 400, naming the problem.

Access: an API key with languages:write (or a master above it: languages:all, admin:all). A signed-in person may call it as far as their own permissions allow; anyone else gets 403.

Rate limit: the key’s own writes-per-minute limit, set when the key is created (default 120); over it, 429 with Retry-After.

PATCH

site-languages

{_id}

cURL

curl --request PATCH \
  --url https://{host}/api/v1/site-languages/{_id} \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '{}'

{
  "_id": "<string>",
  "type": "<string>",
  "createdAt": "2023-11-07T05:31:56Z",
  "updatedAt": "2023-11-07T05:31:56Z",
  "mainLanguageName": "English",
  "languages": []
}

{
  "name": "<string>",
  "message": "<string>",
  "data": {}
}

{
  "name": "<string>",
  "message": "<string>",
  "data": {}
}

{
  "name": "<string>",
  "message": "<string>",
  "data": {}
}

{
  "name": "<string>",
  "message": "<string>",
  "data": {}
}

{
  "name": "<string>",
  "message": "<string>",
  "data": {}
}

Authorizations

Authorization

string

header

required

Paste your API key as the CMS showed it: fsk_<site>_<key id>_<secret> (issued under API Keys). ApiKey in front of it works too. Leave it empty to read as the public.

Scopes

languages:write

Path Parameters

_id

string

required

The document’s _id: a full id names its own locale and mode (the draft’s …:en:draft, the published one’s …:en:published; no aposMode needed), a bare aposDocId takes the request’s (aposLocale, aposMode).

Body

application/json

SiteLanguages content type

mainLanguageName

string | null

default:English

The language the site is written in first, named as its speakers write it. Its pages keep their addresses as they are (/about).

languages

More languages · object[] | null

Each language gets its own addresses (/fr/about) and its own copy of every page, translated with Localize. A language you remove keeps its translations: add the same code again and they come back.

Show child attributes

Response

Success

SiteLanguages content type

_id

string

required

read-only

The document’s id. On a type with drafts it ends in its locale and mode (…:en:published, …:en:draft): the part before the first colon is its aposDocId, shared by both copies. The {_id} the type’s routes take.

type

string

required

read-only

The document type’s name: always this type’s.

createdAt

string<date-time>

required

read-only

When it was created (ISO 8601).

updatedAt

string<date-time>

required

read-only

When it last changed (ISO 8601).

mainLanguageName

string | null

default:English

The language the site is written in first, named as its speakers write it. Its pages keep their addresses as they are (/about).

languages

More languages · object[] | null

Each language gets its own addresses (/fr/about) and its own copy of every page, translated with Localize. A language you remove keeps its translations: add the same code again and they come back.

Show child attributes

cURL

curl --request PATCH \
  --url https://{host}/api/v1/site-languages/{_id} \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '{}'

{
  "_id": "<string>",
  "type": "<string>",
  "createdAt": "2023-11-07T05:31:56Z",
  "updatedAt": "2023-11-07T05:31:56Z",
  "mainLanguageName": "English",
  "languages": []
}

{
  "name": "<string>",
  "message": "<string>",
  "data": {}
}

{
  "name": "<string>",
  "message": "<string>",
  "data": {}
}

{
  "name": "<string>",
  "message": "<string>",
  "data": {}
}

{
  "name": "<string>",
  "message": "<string>",
  "data": {}
}

{
  "name": "<string>",
  "message": "<string>",
  "data": {}
}

Get started

How the API works

Pages & Site

Content

Media

Forms

Ads & Conversions

Analytics

Signing in (people)

Update a language list

Authorizations

Scopes

Path Parameters

Body

Response