> ## 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. # Clear DQ and/or metadata scores for a table > Clear one or both score types for a table in a single call. Use scope=data_quality to clear DQ tags and rules, scope=metadata to clear the metadata score, or scope=all to clear everything (the Clear All action). Previous data is preserved for history. Running a new assessment restores the score. ## OpenAPI ````yaml /openapi/em-data-readiness-v2.yaml delete /api/data-readiness/data-assets/tables/scores 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/data-assets/tables/scores: delete: tags: - Data Assets summary: Clear DQ and/or metadata scores for a table description: >- Clear one or both score types for a table in a single call. Use scope=data_quality to clear DQ tags and rules, scope=metadata to clear the metadata score, or scope=all to clear everything (the Clear All action). Previous data is preserved for history. Running a new assessment restores the score. operationId: delete_table_scores parameters: - name: fqn in: query required: true schema: type: string minLength: 1 description: >- Fully qualified name of the table (e.g., service.database.schema.table) title: Fqn description: >- Fully qualified name of the table (e.g., service.database.schema.table) - name: scope in: query required: true schema: $ref: '#/components/schemas/ClearScope' description: 'Score type(s) to clear: data_quality, metadata, or all' description: 'Score type(s) to clear: data_quality, metadata, or all' responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/TableScoresClearResult' '404': description: Table 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: ClearScope: type: string enum: - data_quality - metadata - all title: ClearScope description: Score type(s) to clear for a table. TableScoresClearResult: properties: table_fqn: type: string title: Table Fqn description: Fully qualified table name scope: items: $ref: '#/components/schemas/ClearScope' type: array title: Scope description: Score types that were cleared (e.g., ['data_quality', 'metadata']) type: object required: - table_fqn - scope title: TableScoresClearResult description: >- Result of clearing one or more score types for a table. Previous data is preserved for history but no longer visible via the API. Running a new assessment restores the score for that type. 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 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. ````