Skip to main content

Documentation Index

Fetch the complete documentation index at: https://ekso.dev/llms.txt

Use this file to discover all available pages before exploring further.

Sample shape for ConfigContentTemplate.

​
Sample JSON

Copy, edit, paste. Server-set fields (id, created, tenantId, …) are omitted from the example — they’re populated by the server on response. 
{
  "name": "Example name",
  "description": "Example description.",
  "owner": "<content-owner>",
  "isSystem": false,
  "variant": [
    "<config-content-template-variant>"
  ]
}

​
Fields

FieldTypeRequiredNotes
entitystring • nullableServer-setSet by the server. Read-only on writes.
namestringRequired
descriptionstringRequired
ownerContentOwnerRequired
isSystembooleanOptional
variantarray<ConfigContentTemplateVariant>Required
tenantIdstringServer-setSet by the server. Read-only on writes.
idstringServer-setSet by the server. Read-only on writes.
createdstring (date-time)Server-setSet by the server. Read-only on writes.
createdBystringServer-setSet by the server. Read-only on writes.
updatedstring (date-time)Server-setSet by the server. Read-only on writes.
updatedBystringServer-setSet by the server. Read-only on writes.
deletedbooleanServer-setSet by the server. Read-only on writes.

​
Used by

​
Request body

  • POST /api/template/content
  • PUT /api/template/content

​
Response body

  • GET /api/template/content/{id}
  • GET /api/template/content

​
CLI

ekso content-template — see the command branches page for available verbs. Body for create / update verbs typically passed via --data @file.json matching the sample JSON above.