Import an Overlay

Import a complete Customer Overlay top-down: doctypes and fields in one call, optionally published immediately. Blank anchors auto-map to Talonic types.

Import is the fast path for standing up an overlay from a definition you already have. You post the whole thing — name, doctypes, and fields — in one call, and optionally publish it immediately with publish: true. Any doctype you leave without a maps_to anchor is auto-mapped to the best-matching Talonic type by embedding similarity before it is saved, so you do not have to hand-anchor every doctype.

Each doctype carries a key, a name, an optional category, classification signals, and the maps_to Talonic anchor. Each field carries a key plus optional canonical_name, display_name, data_type, synonyms, a doctype_scope (a doctype key, or null/empty/* for a global field), required, format, enum_values, and examples.

Import is idempotent authoring, not a merge: the posted definition becomes the draft wholesale. Keep your overlay definition in version control and re-import it on change, the same way you would apply configuration as code.