Recipe 1 — Use a Corti Standard out of the box

Reference a curated Corti Standard template by UUID with no overrides — the lightest, fastest production path.

Beta

← Back to Customization Cookbook

Scenario: You want a SOAP note, an HPI section, a Plan section — exactly as Corti curates them.

What you do:

1. Discover the section/template UUID for your locale via LIST /documents/sections?lang=en (filter source === "corti" client-side; see Corti Standards).
2. Reference the UUID from POST /documents using Path 1 (plain templateRef).

POST /documents — Path 1 (plain templateRef)

{
  "outputLanguage": "en-US",
  "interactionId": "<your-interaction-id>",
  "templateRef": {
    "templateId": "<your-template-id>"
  }
}

Why this lever: Zero side-effects, fastest path. Corti improvements to the Standard propagate automatically — the next call uses the latest published version. These upstream updates are typically silent (small prompt refinements and quality improvements ship continuously, like many small API releases); only schema-breaking or significant behavior changes are explicitly communicated.

When you’ve outgrown it: You want a different section title, a different writing style, a tighter outputSchema, or one extra section. Move to Recipe 2 (or Recipe 4 if you need to fully decouple from the Standard’s silent updates).

---

Next: Recipe 2 — Inherit from a Corti Standard via inheritFromId