How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Microsoft Purview Glossary API

Operations for managing glossary terms, categories, and assignments

Microsoft Purview Glossary API is one of 44 APIs that Microsoft Purview publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Glossary. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, pricing, a getting-started guide, and an API reference.

This API exposes 19 operations across 10 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://{accountName}.purview.azure.com/catalog, https://{accountName}.purview.azure.com/datamap.

19 operations 10 paths 15 schemas 4 DELETE7 GET5 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{account-name}.purview.azure.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Microsoft Purview Glossary API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the clientCredentials flow, exposing 1 scope. By default, every request must be authenticated.

  • oauth2 — Azure Active Directory OAuth2 authentication

Paths & Operations 19

Across 10 paths, the API surfaces 19 operations — 4 DELETE, 7 GET, 5 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Glossary 19

Operations for managing glossary terms, categories, and assignments

GET
/api/atlas/v2/glossary
Microsoft Purview List all glossaries
listGlossaries 4 params → 200401
POST
/api/atlas/v2/glossary
Microsoft Purview Create a glossary
createGlossary body → 200400401
GET
/api/atlas/v2/glossary/{glossaryId}
Microsoft Purview Get glossary by GUID
getGlossary 1 param → 200401404
PUT
/api/atlas/v2/glossary/{glossaryId}
Microsoft Purview Update a glossary
updateGlossary 1 param body → 200401
DELETE
/api/atlas/v2/glossary/{glossaryId}
Microsoft Purview Delete a glossary
deleteGlossary 1 param → 204401404
GET
/api/atlas/v2/glossary/{glossaryId}/terms
Microsoft Purview List terms in glossary
listGlossaryTerms 4 params → 200401
GET
/api/atlas/v2/glossary/{glossaryId}/categories
Microsoft Purview List categories in glossary
listGlossaryCategories 4 params → 200401
POST
/api/atlas/v2/glossary/term
Microsoft Purview Create a glossary term
createGlossaryTerm 1 param body → 200400401
GET
/api/atlas/v2/glossary/term/{termId}
Microsoft Purview Get glossary term by GUID
getGlossaryTerm 1 param → 200401404
PUT
/api/atlas/v2/glossary/term/{termId}
Microsoft Purview Update a glossary term
updateGlossaryTerm 2 params body → 200401
DELETE
/api/atlas/v2/glossary/term/{termId}
Microsoft Purview Delete a glossary term
deleteGlossaryTerm 1 param → 204401
POST
/api/atlas/v2/glossary/terms
Microsoft Purview Create glossary terms in bulk
createGlossaryTerms body → 200400401
POST
/api/atlas/v2/glossary/category
Microsoft Purview Create a glossary category
createGlossaryCategory body → 200400401
GET
/api/atlas/v2/glossary/category/{categoryId}
Microsoft Purview Get glossary category by GUID
getGlossaryCategory 1 param → 200401404
PUT
/api/atlas/v2/glossary/category/{categoryId}
Microsoft Purview Update a glossary category
updateGlossaryCategory 1 param body → 200401
DELETE
/api/atlas/v2/glossary/category/{categoryId}
Microsoft Purview Delete a glossary category
deleteGlossaryCategory 1 param → 204401
GET
/api/atlas/v2/glossary/terms/{termId}/assignedEntities
Microsoft Purview List entities assigned with term
listEntitiesAssignedWithTerm 4 params → 200401
POST
/api/atlas/v2/glossary/terms/{termId}/assignedEntities
Microsoft Purview Assign term to entities
assignTermToEntities 1 param body → 204401
DELETE
/api/atlas/v2/glossary/terms/{termId}/assignedEntities
Microsoft Purview Remove term assignment from entities
deleteTermAssignmentFromEntities 1 param body → 204401

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are AtlasGlossaryTerm (13 properties), AtlasGlossary (9 properties), AtlasGlossaryCategory (9 properties), AtlasGlossary_2 (9 properties). Each schema is shown below with its type and property counts.

AtlasGlossaryTerm
object
A glossary term
13 properties
ResourceLink
object
2 properties
TimeBoundary
object
3 properties
AtlasRelatedTermHeader
object
7 properties
AtlasTermCategorizationHeader
object
5 properties
AtlasRelatedObjectId
object
8 properties
AtlasRelatedCategoryHeader
object
5 properties
AtlasGlossaryHeader
object
3 properties
AtlasClassification
object
A classification instance
8 properties
AtlasGlossaryCategory
object
A glossary category
9 properties
AtlasGlossary
object
A glossary object
9 properties
AtlasGlossaryTerm_2
object
8 properties
AtlasRelatedTermHeader_2
object
3 properties
AtlasRelatedCategoryHeader_2
object
3 properties
AtlasGlossary_2
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-purview-glossary-api-openapi.yml Raw ↑

Other APIs Microsoft Purview publishes across the network.

Microsoft Purview Accounts API
Microsoft Purview Approval API
Microsoft Purview Business Domains API
Microsoft Purview Cases API
Microsoft Purview Classification Rules API
Microsoft Purview Critical Data Elements API
Microsoft Purview Custodians API
Microsoft Purview Data Products API
Microsoft Purview Data Profiling API
Microsoft Purview Data Quality Rules API
Microsoft Purview Data Quality Scans API
Microsoft Purview Data Quality Scores API
Where this information came from

This is an independent, third-party profile of Microsoft Purview Glossary API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.