> ## Documentation Index > Fetch the complete documentation index at: https://docs.emergence.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get a glossary term by ID > Get a single glossary term by its ID. ## OpenAPI ````yaml /openapi/em-data-readiness-v2.yaml get /api/data-readiness/glossary/terms/{term_id} openapi: 3.1.0 info: title: EM Data Readiness Service description: Data Readiness Service API for managing workflows, metrics, and data quality version: 4.3.0-dev1 servers: [] security: - BearerAuth: [] tags: - name: Health description: Service health monitoring. Check service status and version information. - name: Root description: Root endpoint providing service information and navigation links. - name: Configuration description: Service configuration endpoints. View current configuration values. - name: Workflows description: >- Workflow configuration and execution management. Create, configure, and run data quality workflows including definitions, configurations, runs, and tasks. - name: Data Assets description: >- Data catalog entity management. Manage databases, schemas, and tables metadata. - name: Metrics description: >- Data quality metrics and scorecards. Calculate scores, view trends, and analyze dimensions. - name: Violations description: >- Data quality violation management. View, acknowledge, and remediate detected violations. - name: Glossary description: >- Business glossary management. Create, verify, and organize business terms and definitions. paths: /api/data-readiness/glossary/terms/{term_id}: get: tags: - Glossary summary: Get a glossary term by ID description: Get a single glossary term by its ID. operationId: get_glossary_term parameters: - name: term_id in: path required: true schema: type: string title: Term Id responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/GlossaryTermResponse' '404': description: Term not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' '500': description: Internal Server Error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - BearerAuth: [] components: schemas: GlossaryTermResponse: properties: id: type: string title: Id description: Term ID (em-runtime Memory ID) term: type: string title: Term description: Term name definition: type: string title: Definition description: Term definition domain: type: string title: Domain description: Business domain type: $ref: '#/components/schemas/GlossaryTermType' description: Concept or Vocabulary status: type: string title: Status description: Verified, Unverified, or Conflicting owner: type: string title: Owner description: Term owner last_updated: type: string title: Last Updated description: Human-readable last updated date related_terms: items: type: string type: array title: Related Terms description: Related term names usage_count: type: integer title: Usage Count description: Usage count (placeholder) default: 0 version: type: string title: Version description: Version number as string data_sources: items: type: string type: array title: Data Sources description: Fully qualified table names where this term appears source_schema: anyOf: - type: string - type: 'null' title: Source Schema description: Linked schema FQN source_reference_file: anyOf: - type: string - type: 'null' title: Source Reference File description: Source reference document conflict_reason: anyOf: - type: string - type: 'null' title: Conflict Reason description: Conflict reason (when status=Conflicting) is_generated: type: boolean title: Is Generated description: Whether AI-generated default: false custom_tags: items: type: string type: array title: Custom Tags description: Custom tags resource_uri: anyOf: - type: string - type: 'null' title: Resource Uri description: Parent DB connection resource_uri type: object required: - id - term - definition - domain - type - status - owner - last_updated - version title: GlossaryTermResponse description: A single glossary term as returned to the UI. ErrorResponse: properties: error: $ref: '#/components/schemas/ErrorInfo' description: >- Error information object containing code, message, and optional details request_id: anyOf: - type: string - type: 'null' title: Request Id description: Request ID for debugging and support examples: - req_abc123xyz type: object required: - error title: ErrorResponse description: >- Standard error response model for API errors. Matches the structure returned by _handle_service_error in workflows/routes.py. The actual API response format is: { "error": { "code": "ERROR_CODE", "message": "Error message", "details": {...} }, "request_id": "optional-request-id" } HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError GlossaryTermType: type: string enum: - Concept - Vocabulary title: GlossaryTermType description: Type of glossary term. ErrorInfo: properties: code: type: string title: Code description: >- Error code identifier (e.g., 'WORKFLOW_NOT_FOUND', 'VALIDATION_ERROR') examples: - WORKFLOW_NOT_FOUND message: type: string title: Message description: Human-readable error message examples: - >- Workflow configuration with id '123e4567-e89b-12d3-a456-426614174000' not found details: anyOf: - additionalProperties: true type: object - type: 'null' title: Details description: >- Additional error details as a dictionary (flexible structure for business logic errors) examples: - workflow_id: 123e4567-e89b-12d3-a456-426614174000 type: object required: - code - message title: ErrorInfo description: >- Nested error information object. Note: This model uses an untyped dict for `details` to match the flexible error structure used throughout the service layer (see WorkflowServiceError and similar). This is distinct from ErrorDetail, which is used for structured validation errors. ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- JWT Bearer token authentication. Include the token in the Authorization header as: `Authorization: Bearer `. The JWT must contain valid client_id, and project_id claims for tenant isolation and SDK routing. ````