> ## Documentation Index > Fetch the complete documentation index at: https://docs.azalt.co/llms.txt > Use this file to discover all available pages before exploring further. # Delete file > Permanently delete a file from both the database and cloud storage. This action cannot be undone. **Required parameter**: - `mediaId`: The unique ID of the file to delete **What happens when you delete**: 1. File record is removed from the database 2. Actual file is deleted from cloud storage 3. All associated metadata is cleaned up 4. Deletion is logged for audit purposes **Security checks**: - You must have proper permissions for the file's related item - Only users in the same organization can delete files - Critical files may be soft-deleted to preserve audit trails **⚠️ Before deleting, consider**: - Are any forms, dashboards, or reports using this file? - Is this file required for compliance or regulatory purposes? - Will deleting this affect other parts of the system? **Good reasons to delete**: - Remove outdated or incorrect documents - Clean up test files or duplicates - Comply with data retention policies - Fulfill user requests for file removal ## OpenAPI ````yaml https://app.azalt.co/api/v1/openapi.json delete /media/{mediaId} openapi: 3.0.3 info: title: Erguvan Public API version: 1.0.0 servers: - url: https://app.azalt.co/api/v1 security: [] paths: /media/{mediaId}: delete: tags: - File summary: Delete file description: >- Permanently delete a file from both the database and cloud storage. This action cannot be undone. **Required parameter**: - `mediaId`: The unique ID of the file to delete **What happens when you delete**: 1. File record is removed from the database 2. Actual file is deleted from cloud storage 3. All associated metadata is cleaned up 4. Deletion is logged for audit purposes **Security checks**: - You must have proper permissions for the file's related item - Only users in the same organization can delete files - Critical files may be soft-deleted to preserve audit trails **⚠️ Before deleting, consider**: - Are any forms, dashboards, or reports using this file? - Is this file required for compliance or regulatory purposes? - Will deleting this affect other parts of the system? **Good reasons to delete**: - Remove outdated or incorrect documents - Clean up test files or duplicates - Comply with data retention policies - Fulfill user requests for file removal operationId: deleteFile parameters: - in: path name: mediaId schema: type: string required: true responses: '200': description: Successful response content: application/json: schema: type: object nullable: true properties: id: type: string required: - id '400': description: Invalid input data content: application/json: schema: $ref: '#/components/schemas/error.BAD_REQUEST' '401': description: Authorization not provided content: application/json: schema: $ref: '#/components/schemas/error.UNAUTHORIZED' '403': description: Insufficient access content: application/json: schema: $ref: '#/components/schemas/error.FORBIDDEN' '404': description: Not found content: application/json: schema: $ref: '#/components/schemas/error.NOT_FOUND' '500': description: Internal server error content: application/json: schema: $ref: '#/components/schemas/error.INTERNAL_SERVER_ERROR' security: - Authorization: [] components: schemas: error.BAD_REQUEST: type: object properties: message: type: string description: The error message example: Invalid input data code: type: string description: The error code example: BAD_REQUEST issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Invalid input data error (400) description: The error information example: code: BAD_REQUEST message: Invalid input data issues: [] error.UNAUTHORIZED: type: object properties: message: type: string description: The error message example: Authorization not provided code: type: string description: The error code example: UNAUTHORIZED issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Authorization not provided error (401) description: The error information example: code: UNAUTHORIZED message: Authorization not provided issues: [] error.FORBIDDEN: type: object properties: message: type: string description: The error message example: Insufficient access code: type: string description: The error code example: FORBIDDEN issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Insufficient access error (403) description: The error information example: code: FORBIDDEN message: Insufficient access issues: [] error.NOT_FOUND: type: object properties: message: type: string description: The error message example: Not found code: type: string description: The error code example: NOT_FOUND issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Not found error (404) description: The error information example: code: NOT_FOUND message: Not found issues: [] error.INTERNAL_SERVER_ERROR: type: object properties: message: type: string description: The error message example: Internal server error code: type: string description: The error code example: INTERNAL_SERVER_ERROR issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Internal server error error (500) description: The error information example: code: INTERNAL_SERVER_ERROR message: Internal server error issues: [] securitySchemes: Authorization: type: http scheme: bearer ````