> ## 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. # Replace Export Preset For Member > Replaces the **name**, **columns** and **row source** of a company member's saved export preset, whoever owns it. The owner, entity type, visibility and default stay as they are. The caller is recorded as the preset's last editor for audit. **`rowSource`** and **`fieldKeys`** follow the same rules as [Create Export Preset For Member](/api-reference/entities/create-export-preset-for-member) for the preset's entity type, and the keys are saved in the order given. `rowSource` is required: send the Object List field for one row per item, or `null` for one row per record. Sending `null` for a preset that had a row source makes it export one row per record. - An unknown key is `400 UnknownExportFieldKey`; the error carries `unknownFieldKeys`. Nothing is saved. - A `rowSource` that is not a declared Object List of the entity is `400 InvalidExportRowSource`. - A `name` another of the owner's presets of that entity type uses (compared case-insensitively, ignoring surrounding spaces) is `409 ExportPresetNameTaken`; the error carries `existingPresetNames`. Keeping the preset's own name is allowed. - An unknown or deleted `presetId`, or one in another company, is `404 NotFoundError`. **Required permission:** `export-preset.edit-for-member` ## OpenAPI ````yaml /openapi/generated-external-api.yaml put /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}: put: tags: - Entities summary: Replace Export Preset For Member description: > Replaces the **name**, **columns** and **row source** of a company member's saved export preset, whoever owns it. The owner, entity type, visibility and default stay as they are. The caller is recorded as the preset's last editor for audit. **`rowSource`** and **`fieldKeys`** follow the same rules as [Create Export Preset For Member](/api-reference/entities/create-export-preset-for-member) for the preset's entity type, and the keys are saved in the order given. `rowSource` is required: send the Object List field for one row per item, or `null` for one row per record. Sending `null` for a preset that had a row source makes it export one row per record. - An unknown key is `400 UnknownExportFieldKey`; the error carries `unknownFieldKeys`. Nothing is saved. - A `rowSource` that is not a declared Object List of the entity is `400 InvalidExportRowSource`. - A `name` another of the owner's presets of that entity type uses (compared case-insensitively, ignoring surrounding spaces) is `409 ExportPresetNameTaken`; the error carries `existingPresetNames`. Keeping the preset's own name is allowed. - An unknown or deleted `presetId`, or one in another company, is `404 NotFoundError`. **Required permission:** `export-preset.edit-for-member` operationId: updateExportPresetForMember parameters: - $ref: '#/components/parameters/companyId' - $ref: '#/components/parameters/exportPresetId' requestBody: required: true content: application/json: schema: type: object additionalProperties: false required: - name - fieldKeys - rowSource properties: name: type: string minLength: 1 maxLength: 255 description: The preset's new name. Surrounding spaces are trimmed. fieldKeys: type: array minItems: 1 description: >- The preset's new columns, in column order. Each key must be offered by the company's export surface for the preset's entity type and `rowSource`, and no key may repeat. items: type: string minLength: 1 rowSource: type: string minLength: 1 nullable: true description: >- The Object List field whose items become the preset's rows, or `null` for one row per record. examples: claimsView: summary: Rename an exposure preset and reorder its columns value: name: Claims view rowSource: null fieldKeys: - id - exposureName paymentsView: summary: Keep a preset one row per payment and replace its columns value: name: Payments view rowSource: payments fieldKeys: - id - __itemIndex - paymentAmount responses: '200': description: The preset as replaced. content: application/json: schema: $ref: '#/components/schemas/ExportPreset' examples: replaced: summary: The replaced preset value: id: 9b1d4e7a-2c3f-4a8b-b6d5-0e7f1a2c3d4e ownerUserId: 3f2b8c1e-6d4a-4b7e-9a15-2c8e0f4d7b91 entityType: exposure name: Claims view visibility: private isDefault: false rowSource: null fieldKeys: - id - exposureName createdAt: '2026-09-25T14:03:22.418Z' updatedAt: '2026-10-12T11:20:07.902Z' '400': description: Bad Request - invalid body, unknown field key, or invalid row source content: application/json: schema: $ref: '#/components/schemas/ExportPresetFieldKeyErrorResponse' examples: unknownFieldKey: summary: A requested field key is not offered by the export surface value: error: code: UnknownExportFieldKey message: >- Unknown export field key for exposure: nope. Only keys the company's exposure export surface offers may be saved. unknownFieldKeys: - nope invalidRowSource: summary: The rowSource is not a declared Object List value: error: code: InvalidExportRowSource message: >- Choose a declared saved Object List for one row per item. '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 '409': description: | Conflict — the name is taken by another of the owner's presets (`ExportPresetNameTaken`, carrying `existingPresetNames`). content: application/json: schema: $ref: '#/components/schemas/ExportPresetConflictErrorResponse' examples: nameTaken: summary: Another of the owner's presets uses this name value: error: code: ExportPresetNameTaken message: >- The owner already has an export preset for exposure named "Claims view". Existing names: claims VIEW existingPresetNames: - claims VIEW '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: ExportPreset: type: object description: A company member's saved export preset. required: - id - ownerUserId - entityType - name - visibility - isDefault - rowSource - fieldKeys - createdAt - updatedAt properties: id: type: string format: uuid ownerUserId: type: string format: uuid description: The member who owns the preset entityType: type: string enum: - event - exposure - quote - submission - person - organization - policy - bordereau description: >- The export screen the preset belongs to, or `bordereau` for the Export Bordereau screen. name: type: string visibility: type: string enum: - private - shared description: >- `private` presets are seen only by their owner; `shared` presets are offered to every member of the company. isDefault: type: boolean description: Whether this is the owner's default preset for its entity type. rowSource: type: string nullable: true description: >- The Object List field the preset exports one row per item of, or `null` for one row per record. fieldKeys: type: array description: The preset's columns, in column order items: type: string createdAt: type: string format: date-time updatedAt: type: string format: date-time ExportPresetFieldKeyErrorResponse: type: object description: | The standard error envelope. For `UnknownExportFieldKey` it also carries `unknownFieldKeys`. required: - error properties: error: type: object required: - code - message properties: code: type: string description: Machine-readable error code example: UnknownExportFieldKey message: type: string description: Human-readable error message userMessages: type: array description: Clean, verbatim-displayable messages items: type: string details: type: array description: Field-level details for body validation errors items: type: object properties: field: type: string message: type: string unknownFieldKeys: type: array description: >- Present on `UnknownExportFieldKey`: every requested key the export surface does not offer. items: type: string 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 ExportPresetConflictErrorResponse: type: object description: | The standard error envelope. For `ExportPresetNameTaken` it also carries `existingPresetNames`. required: - error properties: error: type: object required: - code - message properties: code: type: string description: Machine-readable error code example: ExportPresetNameTaken message: type: string description: Human-readable error message userMessages: type: array description: Clean, verbatim-displayable messages items: type: string existingPresetNames: type: array description: >- Present on `ExportPresetNameTaken`: the names of the owner's other presets for the entity type. items: type: string 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.