# Templates

Use `template_name` to generate with a template your organization can access. If you omit it, Perceptis chooses the same default template experience used in the app.

## Choose a template

In `POST /api/v1/generate` you may set:

```json
"template_name": "Acme Executive"
```

Template names match the templates available to your organization in Perceptis. Use the same display name your team uses in the product.

## Use automatic template selection

If you omit `template_name`, Perceptis uses your organization's default template when one is configured. If no organization default is available, Perceptis uses another template available to your organization. If no template is available, generation still runs with a plain PowerPoint output.

## Ambiguous names

If a name matches more than one accessible template, the API returns `409` with error code `ambiguous_template_name`. Rename one of the templates or choose a unique template name before retrying.

## Practical tips

* Keep template names stable for production integrations.
* Prefer a small set of approved templates for automated generation.
* Treat template names as case-sensitive unless your Perceptis team tells you otherwise.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.perceptis.ai/perceptis-api-v1/templates.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.