> ## Documentation Index > Fetch the complete documentation index at: https://docs.go.aiinsurance.io/llms.txt > Use this file to discover all available pages before exploring further. # Delete Form > Soft-deletes a form from a company instance, addressed by its stable `FM-XXXX` `number` (the value returned by the Upload Form Template and Upload Static Form endpoints). Works for both DOCX templates and static PDF forms. Every version of the form is soft-deleted, so it stops appearing in the app's form library. Forms that were already generated from it keep working — they resolve the specific version they were bound to. Forms-logic rules are configuration and are **not** touched by this call. If the live field-model configuration still contains a rule referencing the form's `number`, deletion is rejected with `409`. Remove the forms-logic rule from the configuration and then retry the delete. **Required permission:** `forms:delete` ## OpenAPI ````yaml /openapi/generated-external-api.yaml delete /api/v1/companies/{companyId}/forms/{number} openapi: 3.0.3 info: title: AI Insurance External API description: External API for AI Insurance platform version: 1.0.0 contact: email: support@aiinsurance.io servers: - url: https://go.aiinsurance.io description: Production security: - ApiKeyAuth: [] paths: /api/v1/companies/{companyId}/forms/{number}: delete: tags: - Forms summary: Delete Form description: > Soft-deletes a form from a company instance, addressed by its stable `FM-XXXX` `number` (the value returned by the Upload Form Template and Upload Static Form endpoints). Works for both DOCX templates and static PDF forms. Every version of the form is soft-deleted, so it stops appearing in the app's form library. Forms that were already generated from it keep working — they resolve the specific version they were bound to. Forms-logic rules are configuration and are **not** touched by this call. If the live field-model configuration still contains a rule referencing the form's `number`, deletion is rejected with `409`. Remove the forms-logic rule from the configuration and then retry the delete. **Required permission:** `forms:delete` operationId: deleteForm parameters: - $ref: '#/components/parameters/companyId' - $ref: '#/components/parameters/formTemplateNumber' responses: '200': description: Form deleted content: application/json: schema: type: object properties: number: type: string description: The number of the deleted form. deleted: type: boolean description: Confirmation that the form was deleted. examples: success: summary: Form deleted value: number: FM-0010 deleted: true '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: > No live form carries the given number (it never existed, or was already deleted). content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: notFound: summary: Unknown or already-deleted number value: error: code: form-template-not-found message: No form template with number FM-0010 was found. userMessages: - No form template with number FM-0010 was found. '409': description: | The live field-model configuration contains a forms-logic rule that references this form. Remove the rule before deleting the form. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: referencedByFormsLogic: summary: Form is still referenced by forms logic value: error: code: form-template-referenced-by-form-logic message: >- Remove the forms-logic rule for "FM-0010" from the field-model configuration before deleting the form template. userMessages: - >- Remove the forms-logic rule for "FM-0010" from the field-model configuration before deleting the form template. '500': $ref: '#/components/responses/InternalServerError' components: parameters: companyId: name: companyId in: path required: true schema: type: string format: uuid description: Company identifier formTemplateNumber: name: number in: path required: true schema: type: string description: > The form template's stable `FM-XXXX` number (as returned by the Upload Form Template endpoint). It identifies the template across all of its versions and is the same value forms-logic rules reference. responses: Unauthorized: description: Unauthorized - Invalid or missing API key content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: missingApiKey: summary: Missing API key value: error: code: AuthenticationError message: API key authentication required userMessages: - API key authentication required invalidApiKey: summary: >- Invalid API key (e.g. unknown key, or a Bearer token used instead of an API key) value: error: code: AuthenticationError message: Invalid API key userMessages: - Invalid API key Forbidden: description: Forbidden - Insufficient permissions content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: insufficientPermissions: summary: Insufficient permissions value: error: code: AuthorizationError message: User is not authorized to perform the requested action userMessages: - User is not authorized to perform the requested action companyMismatch: summary: A valid API key naming another company in the URL value: error: code: AuthorizationError message: API key is not scoped to the requested company userMessages: - API key is not scoped to the requested company InternalServerError: description: Internal Server Error - Unexpected error occurred content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: internalError: summary: Unexpected server error value: error: code: UncaughtActionError message: Uncaught error occurred in userMessages: - An unexpected error occurred. Please try again later. schemas: ErrorResponse: type: object description: Standard error response for all external API endpoints required: - error properties: error: type: object required: - code - message properties: code: type: string description: Machine-readable error code example: VALIDATION_ERROR message: type: string description: Human-readable error message example: 'submissionId: Required field is missing' userMessages: type: array description: >- Clean, verbatim-displayable messages — one entry per failure, free of error-code tags, field paths, and internal noise. Suitable for showing to end users as-is. items: type: string example: - Exposures of type 'company' require an address details: type: array description: Additional details for validation errors (field-level errors) items: type: object properties: field: type: string description: The field that caused the error example: submissionId message: type: string description: Description of the field error example: Required field is missing securitySchemes: ApiKeyAuth: type: apiKey in: header name: Authorization description: >- API key authentication. Send your raw API key as the `Authorization` header value with NO scheme prefix — `Authorization: YOUR-API-KEY`. Do NOT prefix it with `Bearer ` or `ApiKey `, and do not use an `X-API-Key` header; those are not accepted. ````