> ## 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 Export Preset For Member > Deletes a company member's saved export preset, whoever owns it. It leaves the owner's export screen, and every other member's if it was shared. The caller is recorded as the deleter for audit. An unknown or already deleted `presetId`, or one in another company, is `404 NotFoundError`. **Required permission:** `export-preset.delete-for-member` ## OpenAPI ````yaml /openapi/generated-external-api.yaml delete /api/v1/companies/{companyId}/export-presets/{presetId} 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}/export-presets/{presetId}: delete: tags: - Entities summary: Delete Export Preset For Member description: > Deletes a company member's saved export preset, whoever owns it. It leaves the owner's export screen, and every other member's if it was shared. The caller is recorded as the deleter for audit. An unknown or already deleted `presetId`, or one in another company, is `404 NotFoundError`. **Required permission:** `export-preset.delete-for-member` operationId: deleteExportPresetForMember parameters: - $ref: '#/components/parameters/companyId' - $ref: '#/components/parameters/exportPresetId' responses: '200': description: The preset was deleted. content: application/json: schema: type: object required: - id - deleted properties: id: type: string format: uuid description: The ID of the deleted preset deleted: type: boolean description: Confirmation that the preset was deleted examples: success: summary: Preset deleted value: id: 9b1d4e7a-2c3f-4a8b-b6d5-0e7f1a2c3d4e deleted: true '400': description: Bad Request - `presetId` is not a UUID content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: invalidPresetId: summary: The presetId is not a UUID value: error: code: VALIDATION_ERROR message: 'presetId: Invalid GUID' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: No such preset in this company content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: notFound: summary: Preset not found value: error: code: NotFoundError message: >- Export preset 9b1d4e7a-2c3f-4a8b-b6d5-0e7f1a2c3d4e not found '500': $ref: '#/components/responses/InternalServerError' security: - BearerAuth: [] - ApiKeyAuth: [] components: parameters: companyId: name: companyId in: path required: true schema: type: string format: uuid description: Company identifier exportPresetId: name: presetId in: path required: true schema: type: string format: uuid description: Export preset identifier 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 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. 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. BearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- User-principal OAuth 2.0 Bearer authentication. Send a user-scoped Auth0 access token (audience = the app API audience) as `Authorization: Bearer `. The request resolves to the user's identity and is authorized by their Role on the `{companyId}` in the path — the same role-based permissions the web app enforces. This is the path the MCP connector uses to act on a user's behalf; endpoints that accept it list both `BearerAuth` and `ApiKeyAuth`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.