domain-is-template=yes. The domain is otherwise normal — it can hold users, queues, attendants and audio like any other, and what it holds is exactly what a domain provisioned from it receives.GET /domains excludes them unless asked (include-templates=yes or only), so they do not pad an administrator's domain grid or its counts. A request naming a single domain still reads it.{{TOKEN}} placeholders in names and descriptions where each provisioned domain should differ — {{STORE_NAME}}, {{STORE_NUMBER}} — then GET /domains/{domain}/template-variables will discover them and a caller can supply values at provisioning time. Set TEMPLATE_MAIN_DEST_TYPE and TEMPLATE_MAIN_DEST_NAME in the template's UI configuration to say where a provisioned domain's main number should land.GET /domains/templates for the catalog of templates and what each one holds.Authorization: Bearer ********************curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/domains' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"domain": "franchise-1",
"reseller": "{{reseller}}",
"description": "Franchise store template",
"domain-is-template": "yes",
"caller-id-name": "{{STORE_NAME}}",
"area-code": "619"
}'{
"code": 0,
"message": "string",
"warnings": [
"string"
]
}