POST /v1/glossaryTerms
Create a Glossary Term
Create a new glossary term with definition, synonyms, related terms, references, and governance metadata within a glossary hierarchy using the Collate REST API.
POST
POST /v1/glossaryTerms
Create a Glossary Term
Create a new glossary term within a glossary.Body Parameters
Name of the glossary term. Must be unique within the parent glossary or parent term.
Fully qualified name of the parent glossary (e.g.,
BusinessGlossary).Human-readable display name for the glossary term.
Description of the glossary term in Markdown format.
Fully qualified name of the parent glossary term for creating nested terms (e.g.,
BusinessGlossary.Revenue).Array of synonym strings for this term.
Array of fully qualified names of related glossary terms.
Array of owner references (users or teams) to assign to the glossary term.
Array of classification tags to apply.
Fully qualified name of the domain to assign for governance purposes.
Visual styling for the glossary term.
POST /v1/glossaryTerms
Returns
Returns the created glossary term object with all specified properties and system-generated fields.Response
Unique identifier for the glossary term (UUID format).
Glossary term name.
Fully qualified name in format
glossary.termName or glossary.parent.child.Human-readable display name.
Description of the glossary term in Markdown format.
List of synonym strings for this term.
Reference to the parent glossary.
Child glossary term references.
Related glossary term references.
List of owners assigned to the glossary term.
Classification tags applied to the glossary term.
Visual styling for the term.
Version number for the entity (starts at 0.1).
Create or Update (PUT)
UsePUT /v1/glossaryTerms instead of POST to perform an upsert. If a glossary term with the same fullyQualifiedName already exists, it will be updated; otherwise, a new glossary term is created. The request body is the same as POST.
PUT will not return a 409 conflict error if the entity already exists — it will update the existing entity instead. However, for certain fields (such as description, tags, owners, and custom properties), PUT preserves an already-populated value instead of overwriting it with an empty or omitted one — the exact behavior depends on the field and the calling user or bot’s permissions, not a blanket rule. See Entity Update Behavior for the full preserve/merge rules. Use PATCH to intentionally replace an existing value.