Sign in

v1

latestOpenAPI 3.1.02026-07-2683111282.3 KB
Content Resource Bundle Operations

Get a resource bundle in a specific project

Get a resource bundle in a specific project.

Resource bundles are also documents which are collections of key message pairs. The locale specific messages can be defined in a single structure. The projects are supported on resource bundles.

Resource bundles are mostly defined with the locale based value sets. The value sets are not restricted to use with locales only though. Any other grouping can also be defined with a resource bundle document. The design also supports custom value sets apart from locales.

A Resource bundle in core may be have changes that aren't yet published, these are stored in a separate variant of the bundle (the 'unpublished' variant). When requesting a bundle for core, the 'published' variant is retrieved, unless there is none (the bundle has never been published yet), in which case the unpublished variant is fetched.

get/project/{project_id}/resourcebundles/{resource_bundle_path}

Path parameters

project_idstring required

specifies the project content is fetched from

resource_bundle_pathstring required

Path of a resource bundle. This is the absolute path to the resource bundle, including the resource bundle name

Response

OK

namestring required

identifying name of this resource bundle. Only valid characters are lowercase alphanumeric, dash, dot, and underscore. This value appears in URLs. The value must alsomatch the document name(last part of the path) in the document path.

displayNamestring required

name of this resource bundle. Used in labels in the CMS UI

idstring required

id of the resource bundle which is expected to be unique in content application. The resource bundle is assigned with this unique id.

pathstring required

absolute path of this resource bundle in the content repository