Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.corti.ai/llms.txt

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

← Back to Guided Synthesis overview Use this when a published template already encodes everything you need. The base template is not modified, and no new template is persisted as a side-effect of the call. This is the lightest path — ideal for production traffic. 
// Replace these with your values
const INTERACTION_ID = "<your-interaction-id>";
const TEMPLATE_ID = "<your-template-id>";

const result = await client.documents.generate({
  outputLanguage: "en-US",
  interactionId: INTERACTION_ID,
  templateRef: { templateId: TEMPLATE_ID },
});
Pin a specific version when you need reproducibility against a known version (otherwise the template’s currently published version is used): 
"templateRef": {
  "templateId":        "<your-template-id>",
  "templateVersionId": "<your-version-id>"
}

​
When to use this path

ScenarioWhy Path 1
Production ambient flow where every encounter uses the same templateReproducible, fastest, no auto-generated aggregate to manage.
You want full traceability via a known templateVersionIdPin the version explicitly — the response’s templateId / templateVersionId match your request.
You have no per-call tweaks todayIf a tweak becomes needed later, you can move to Path 2 (templateRef + overrides) without changing the rest of your integration.
If you’re new to Guided Synthesis, this is the path to start with. Once it works end-to-end, layer in overrides (Path 2) or assembly (Path 3) as your use case grows.

Guided Synthesis overview

Shared concepts: input context, response shape, errors, 30-day retention.

Path 2 — templateRef + overrides

Keep your base template, patch a section’s title, instructions or schema for a single call.