> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Delete an XSD Schema > Use this endpoint to delete an XSD schema. An active provider configuration or an active workflow that references the schema blocks the delete with 409. References from inactive workflows or disabled provider configurations do not block: the delete proceeds and the response carries the warnings. A schema with no references at all returns 204. ## OpenAPI ````yaml en/openapi/v3-current/flowker.yaml delete /v1/xsd-schemas/{id} openapi: 3.1.0 info: description: >- Complete API reference for Flowker workflow orchestration services including catalog management, workflow definitions, executor configurations, provider configurations, and workflow executions. title: Flowker API version: 1.2.0 servers: - url: https://flowker.sandbox.lerian.net security: - BearerAuth: [] tags: - name: Catalog API description: >- Browse built-in providers, executors, and triggers available in the Flowker catalog. - name: Workflows API description: >- Create, update, activate, deactivate, clone, and delete workflow definitions. - name: Executions API description: Start workflow executions and track their status and results. - name: Executor Configurations API description: >- List, inspect, update, and delete the executor configuration records a deployment holds. - name: Provider Configurations API description: >- Create, update, enable, and disable the provider configurations that workflow nodes call through. - name: Dashboard API description: >- Retrieve aggregated summaries of workflows and executions for operational dashboards. - name: Webhooks API description: >- Receive webhook callbacks from external systems to trigger workflow executions. - name: Schedule API description: >- Inspect a workflow's upcoming, skipped, and parked scheduled occurrences, and run or discard the parked ones. - name: Schema Registry API description: >- Publish global OpenAPI specification versions for native services and pin the version each tenant resolves against. - name: OpenAPI Schemas API description: >- Upload, inspect, and delete the tenant's external OpenAPI schemas, and derive the contract of a single operation. - name: XSD Schemas API description: >- Upload, inspect, and delete the tenant's XSD schemas used to validate XML webhook payloads. paths: /v1/xsd-schemas/{id}: delete: tags: - XSD Schemas API summary: Delete an XSD Schema description: >- Use this endpoint to delete an XSD schema. An active provider configuration or an active workflow that references the schema blocks the delete with 409. References from inactive workflows or disabled provider configurations do not block: the delete proceeds and the response carries the warnings. A schema with no references at all returns 204. operationId: deleteXSDSchema parameters: - description: XSD Schema ID (UUID). in: path name: id required: true schema: description: XSD Schema ID (UUID). type: string example: 018f3e2a-1c4d-7b9e-a1b2-c3d4e5f6a7b8 responses: '200': content: application/json: schema: $ref: '#/components/schemas/SchemaDeleteWarningsOutput' description: >- Indicates that the request was successful and the response contains the requested data. '204': description: >- Indicates that the schema was deleted and had no blocking or warning references. '400': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates that the request was malformed or contained invalid parameters. '404': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: Indicates that the requested resource could not be found. '409': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates that the request could not be completed due to a conflict with the current state of the resource. '422': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates that the request was well-formed but contains semantic errors that prevent processing. '500': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates an unexpected internal error. If this persists, please contact support. components: schemas: SchemaDeleteWarningsOutput: additionalProperties: false properties: providerConfigurationWarnings: items: $ref: '#/components/schemas/SchemaReferenceRef' type: - array - 'null' warnings: items: $ref: '#/components/schemas/SchemaReferenceRef' type: - array - 'null' required: - warnings type: object ErrorResponse: properties: code: description: Stable, machine-readable Flowker error code. example: FLK-0001 type: string detail: description: >- Human-readable explanation of this occurrence. Responses with a status of 500 or above carry a fixed generic message. example: name is a required field type: string errors: description: Per-field entries for a request that failed validation. items: $ref: '#/components/schemas/ErrorDetail' type: array instance: description: URI reference identifying this specific occurrence. example: /v1/workflows format: uri type: string status: description: HTTP status code. example: 400 type: integer title: description: >- Standard HTTP reason phrase for the status. It does not change per error code. example: Bad Request type: string type: description: >- URI reference identifying the error. Always the error catalog base followed by the code. example: https://errors.lerian.studio/v1/FLK-0001 format: uri type: string type: object SchemaReferenceRef: additionalProperties: false properties: id: type: string example: 018f3e2a-1c4d-7b9e-a1b2-c3d4e5f6a7b8 name: type: string example: KYC Provider required: - id - name type: object ErrorDetail: properties: location: description: Where the problem is, such as body.nodes or path.id. example: body.nodes type: string message: description: Description of the field-level problem. example: expected array length >= 1 type: string value: description: The value that caused the error, when it is safe to echo. type: object securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- JWT bearer token issued by the identity provider. Send it in the Authorization header as `Bearer `. ````