> ## 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. # Reset Approval Config > Resets the company's invoice-approval configuration to the DEFAULT — custom rules off, so every in-app user with the approve capability may approve any invoice. Implemented as a delete of the company's approval-config document; the absence of a document IS the default. **Idempotent.** A company that has no configuration returns `{ "deleted": false }` and still `200`. Nothing else is touched: no invoice, no journal record, no ledger row — the approval configuration is plain configuration, not books, which is why this operation takes no `If-Match` and no `actionId`. **Scope.** This governs the IN-APP approve action only. An API caller's own approval authority is the `company.payment:approve` permission on its key and was never derived from this configuration, so resetting it changes nothing about what an API key may [approve](/api-reference/financials/approve-invoice). **Required permission:** `company.payment:configure` ## OpenAPI ````yaml /openapi/generated-external-api.yaml delete /api/v1/companies/{companyId}/financials/config/approvals 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}/financials/config/approvals: delete: tags: - Financials summary: Reset Approval Config description: > Resets the company's invoice-approval configuration to the DEFAULT — custom rules off, so every in-app user with the approve capability may approve any invoice. Implemented as a delete of the company's approval-config document; the absence of a document IS the default. **Idempotent.** A company that has no configuration returns `{ "deleted": false }` and still `200`. Nothing else is touched: no invoice, no journal record, no ledger row — the approval configuration is plain configuration, not books, which is why this operation takes no `If-Match` and no `actionId`. **Scope.** This governs the IN-APP approve action only. An API caller's own approval authority is the `company.payment:approve` permission on its key and was never derived from this configuration, so resetting it changes nothing about what an API key may [approve](/api-reference/financials/approve-invoice). **Required permission:** `company.payment:configure` operationId: resetFinancialsApprovalConfig parameters: - $ref: '#/components/parameters/companyId' responses: '200': description: The configuration was reset (or was already at the default) content: application/json: schema: type: object additionalProperties: false required: - deleted properties: deleted: type: boolean description: >- `true` when a stored configuration was removed, `false` when the company was already on the default examples: deleted: summary: A stored configuration was removed value: deleted: true alreadyDefault: summary: The company was already on the default value: deleted: false '400': description: Bad Request — an unknown query parameter content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '500': $ref: '#/components/responses/InternalServerError' components: parameters: companyId: name: companyId in: path required: true schema: type: string format: uuid description: Company 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 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. ````