Using the API is two phases: a one-time template setup, then a request per deck. The workflow is the same whether you’re calling it from a script, an internal pipeline, or an AI agent.Documentation Index
Fetch the complete documentation index at: https://duomi.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Steps 1–2 happen once per template (teal). Steps 3–5 happen on every generation (white).
1. Upload template
You upload your.pptx template — the file that defines your fonts, colours, table styles, chart presets, and master layouts. Each template gets a stable ID you reference in later requests.
2. Service analyzes the template
The service inspects your template and returns a description of each slide — how many columns each table has, what categories each chart expects, where each text block sits. You use that description to know what data to send for each slide.3. Compose request from the analysis
Build a JSON payload that matches the analysis: pick which template slides to use, fill in the data for each one (rows, chart series, text, logos). The shape of the payload follows directly from what the analysis exposed.4. API generates the deck
Submit the request. The API runs the deck against your template asynchronously and returns a generation ID. The client polls until it’s ready — typical decks finish in seconds.5. Download .pptx
Once the generation reports as ready, fetch the finished .pptx. The output looks exactly like your template, with the data you supplied populated into the right places.
AI agent workflow
The same five steps map onto an AI agent’s run. Setup is done once by a human; everything else is the agent’s job per request.| Step | Who does it | What the agent does |
|---|---|---|
| 1. Upload template | Developer / admin | — (handled at setup) |
| 2. Service analyzes the template | Developer / admin | — (handled at setup; agent receives the template_id) |
| 3. Compose request from the analysis | Agent | Pulls data from its sources (CRM, financial models, research notes, call transcripts), reads the template’s analysis to see what each slide expects, and assembles the JSON request |
| 4. API generates the deck | Agent | Calls the generate endpoint and polls for completion |
5. Download .pptx | Agent | Fetches the file and delivers it (drive upload, email, chat reply, etc.) |
From your AI agent’s perspective
Steps 1–2 are setup — a developer or admin uploads the template once and shares thetemplate_id with the agent. The agent only runs steps 3–5 on each request.
The agent never has to know your brand. Fonts, colours, table styles, and chart presets all come from the template that was uploaded once — the agent only handles the data and the slide structure.