Skip to content

List where a template is used

GET
/content/management/v1/templates/{id}/usages/closure
curl --request GET \
--url https://api.ebitex.io/content/management/v1/templates/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/usages/closure \
--header 'Authorization: Bearer <token>'

Lists everything that depends on a template: presentations in components and pages, contracts whose presentation fields allow it, and pages that restrict their children to it. These are the dependents that block deleteTemplate.

Each item is { kind, id, name, detail, path }, where kind is component, node or contract, detail says why it depends on the template, and path is a page’s path. The list is not narrowed by folder access.

Key: a management key with content.management.read.

id
required
string format: uuid

{ "items": [ { "kind": "node", "id": "…", "name": "…", "detail": "…", "path": "/about" } ] }

missing_api_key or invalid_api_key: no key was sent, or it is unknown, revoked or expired.

payment_required: the organization’s subscription needs attention.

scope_denied: the key lacks this route’s scope. tier_required: the Content Management API needs the Pro plan or above. ip_denied: the caller’s address is outside the key’s allowed ranges. app_not_available: Content is not enabled for the organization.

No template with this id exists in the key’s environment.

Rate limit or quota exceeded; Retry-After says how long to wait. too_many_failed_authentications: too many bad keys from this address.