Changelog

Site owners can exclude specific fields, properties, or canvas content from AI translation using the Localization panel in the Designer. These endpoints now expose those exclusion rules through a new translatable query parameter. Translation pipeline integrations can fetch exactly the content that should be translated, without tracking exclusion rules themselves.

New parameter

Pass translatable=true along with a secondary locale to return only content that hasn’t been excluded from translation for that locale:

• Get page content: returns only page fields not excluded for the requested locale.
• Get component content and get component properties: return only canvas content and properties not excluded for the requested locale.
• List and get collection items, including their live counterparts: return only collection fields not excluded for the requested locale.

Only exclusion rules scoped to manual translation are respected — rules scoped only to automatic translation don’t affect the response. Omitting translatable returns the same response as before this parameter existed. Setting translatable=true without also specifying a secondary locale returns a 400 error, since exclusions are resolved per locale.