> ## 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 All Policies > **Hard-deletes every Policy record for the company.** The wipe removes Policy anchors, every live and archived transaction, transaction deltas, segments, relationship rows touching a Policy, and Policy-scoped sequence counters. Other entity types, company configuration, financial records, and financial configuration are kept. Use this endpoint with the other reset operations when a breaking configuration import must be retried. Policy is intentionally outside the generic entity CRUD API, so `POST .../entities/policy/deleteAll` remains invalid; this dedicated Policy route is the complete reset surface. **Guarded.** If financials holds a live claim on any Policy, or a live Quote or Event still references one (including an in-flight renewal draft), the whole wipe returns `409` and nothing is deleted. Clear financial records with `POST .../financials/deleteAll` and delete the referring records first, then retry. **Sandbox only.** Live and Retired companies return `409` without deleting data. A successful request is idempotent: retrying after the wipe succeeds with `deletedRecords: 0`. **Required permission:** `company.reset` — the **Admin** role holds it. ## OpenAPI ````yaml /openapi/generated-external-api.yaml post /api/v1/companies/{companyId}/policies/deleteAll 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}/policies/deleteAll: post: tags: - Policies summary: Delete All Policies description: > **Hard-deletes every Policy record for the company.** The wipe removes Policy anchors, every live and archived transaction, transaction deltas, segments, relationship rows touching a Policy, and Policy-scoped sequence counters. Other entity types, company configuration, financial records, and financial configuration are kept. Use this endpoint with the other reset operations when a breaking configuration import must be retried. Policy is intentionally outside the generic entity CRUD API, so `POST .../entities/policy/deleteAll` remains invalid; this dedicated Policy route is the complete reset surface. **Guarded.** If financials holds a live claim on any Policy, or a live Quote or Event still references one (including an in-flight renewal draft), the whole wipe returns `409` and nothing is deleted. Clear financial records with `POST .../financials/deleteAll` and delete the referring records first, then retry. **Sandbox only.** Live and Retired companies return `409` without deleting data. A successful request is idempotent: retrying after the wipe succeeds with `deletedRecords: 0`. **Required permission:** `company.reset` — the **Admin** role holds it. operationId: deleteAllPolicies parameters: - $ref: '#/components/parameters/companyId' responses: '200': description: Every Policy record was deleted content: application/json: schema: type: object required: - deletedRecords properties: deletedRecords: type: integer description: >- Total rows removed across Policy transaction storage, anchors, relationships, and sequence counters. examples: success: summary: Policy data deleted value: deletedRecords: 42 alreadyEmpty: summary: Safe retry after the Policy data was already deleted value: deletedRecords: 0 '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '409': description: >- Conflict - nothing was deleted because financials or live entity references still depend on a Policy, or the company is not in Sandbox mode. content: application/json: schema: type: object required: - error properties: error: type: object required: - code - message properties: code: type: string message: type: string userMessages: type: array items: type: string blockers: type: array items: type: object required: - entityType - count properties: entityType: type: string count: type: integer financialBlockers: type: object properties: liveInvoiceCount: type: integer nonzeroBalanceCount: type: integer blockedEntityCount: type: integer sampleBlockedEntityIds: type: array maxItems: 10 items: type: string format: uuid examples: blockedByReferences: summary: A live Quote still references a Policy value: error: code: DeleteBlockedByReferences message: >- Cannot delete Policy: still referenced by 1 Quote. Detach these references first. blockers: - entityType: Quote count: 1 blockedByFinancials: summary: Financials still holds a live Policy claim value: error: code: DeleteBlockedByFinancials message: >- Cannot delete all Policy records — financials still holds a live claim on 1 record of this type: 1 live linked invoice (voided invoices still block). Nothing was deleted. To proceed, first clear the company's financial records (POST /api/v1/companies/{companyId}/financials/deleteAll — Sandbox only; financial configuration is kept), then retry this request. financialBlockers: liveInvoiceCount: 1 nonzeroBalanceCount: 0 blockedEntityCount: 1 sampleBlockedEntityIds: - 550e8400-e29b-41d4-a716-446655440001 companyModeConflict: summary: Live mode forbids the wipe value: error: code: CompanyModeConflict message: >- Company mode "live" does not allow bulk-deleting policy data. Only Sandbox companies may be cleared. '500': $ref: '#/components/responses/InternalServerError' components: parameters: companyId: name: companyId in: path required: true schema: type: string format: uuid description: Company identifier 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 code: type: string description: Stable problem code for this individual validation failure example: BLANK_LIST_ELEMENT reason: type: string description: Stable reason the value violates its canonical contract example: blank-list-element expected: type: string description: The expected canonical value contract example: nonblank trimmed string 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. ````