> ## 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. # Re-open Event > Re-opens a closed event (a claim or an incident) as of a date you choose, in one atomic call: the event's status returns to `open`, its **Close Date** is cleared, and a `reopen` entry is appended to the event's open/close-history log. **Use this instead of setting `eventStatus`.** As with [Close Event](/api-reference/event-lifecycle/close-event), a `PATCH` to `/entities/event/{entityId}` that changes `eventStatus` is rejected with a `409` (`GuardedStatusFieldWrite`) — the status and the log move together. **`effectiveOnDate` is required.** It is the date the claim reports as re-opened on, and the platform has no way to infer it. It is also what preserves the previous close date: clearing **Close Date** would otherwise lose it, and the log entry is what a claim's "previously closed on" is read from. **The log cannot run backwards.** `effectiveOnDate` must be on or after the last entry already in the event's log — in practice, on or after the close it reverses. An earlier date returns `409` (`EventLifecycleDateOutOfOrder`) naming the date it has to clear; the same day as the close is allowed. **Required permission:** `company.claim:create` ## OpenAPI ````yaml /openapi/generated-external-api.yaml post /api/v1/companies/{companyId}/events/{eventId}/reopen 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}/events/{eventId}/reopen: post: tags: - Event Lifecycle summary: Re-open Event description: > Re-opens a closed event (a claim or an incident) as of a date you choose, in one atomic call: the event's status returns to `open`, its **Close Date** is cleared, and a `reopen` entry is appended to the event's open/close-history log. **Use this instead of setting `eventStatus`.** As with [Close Event](/api-reference/event-lifecycle/close-event), a `PATCH` to `/entities/event/{entityId}` that changes `eventStatus` is rejected with a `409` (`GuardedStatusFieldWrite`) — the status and the log move together. **`effectiveOnDate` is required.** It is the date the claim reports as re-opened on, and the platform has no way to infer it. It is also what preserves the previous close date: clearing **Close Date** would otherwise lose it, and the log entry is what a claim's "previously closed on" is read from. **The log cannot run backwards.** `effectiveOnDate` must be on or after the last entry already in the event's log — in practice, on or after the close it reverses. An earlier date returns `409` (`EventLifecycleDateOutOfOrder`) naming the date it has to clear; the same day as the close is allowed. **Required permission:** `company.claim:create` operationId: reopenEvent parameters: - $ref: '#/components/parameters/companyId' - $ref: '#/components/parameters/eventIdPath' requestBody: required: true content: application/json: schema: type: object required: - effectiveOnDate properties: effectiveOnDate: $ref: '#/components/schemas/EventLifecycleDate' examples: reopenOnDate: summary: Re-open the claim effective 1 September 2026 value: effectiveOnDate: year: 2026 month: 9 day: 1 responses: '200': description: The event was re-opened. content: application/json: schema: type: object required: - eventId - eventStatus properties: eventId: type: string format: uuid description: The event that was re-opened. eventStatus: type: string enum: - open description: The event's status after the call. examples: reopened: summary: Event re-opened value: eventId: 550e8400-e29b-41d4-a716-446655440020 eventStatus: open '400': description: > `effectiveOnDate` is missing, incomplete, outside the 1900-2200 window, or not a real calendar day; or `eventId` is not a UUID. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: No event with the given id exists for this company. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: > The event cannot be re-opened: it is not `closed` (`EventNotClosed`), or `effectiveOnDate` is earlier than the last entry in its open/close-history log (`EventLifecycleDateOutOfOrder`). content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: notClosed: summary: Event is not closed value: error: code: EventNotClosed message: >- Event 550e8400-e29b-41d4-a716-446655440020 is not closed and cannot be reopened userMessages: - >- Event 550e8400-e29b-41d4-a716-446655440020 is not closed and cannot be reopened dateOutOfOrder: summary: The re-open date precedes the close it reverses value: error: code: EventLifecycleDateOutOfOrder message: >- Event 550e8400-e29b-41d4-a716-446655440020 cannot record a lifecycle action effective 2026-02-15: it is earlier than the last entry in the open/close-history log (2026-03-01) userMessages: - >- Event 550e8400-e29b-41d4-a716-446655440020 cannot record a lifecycle action effective 2026-02-15: it is earlier than the last entry in the open/close-history log (2026-03-01) '500': $ref: '#/components/responses/InternalServerError' components: parameters: companyId: name: companyId in: path required: true schema: type: string format: uuid description: Company identifier eventIdPath: name: eventId in: path required: true schema: type: string format: uuid description: Event (claim or incident) identifier schemas: EventLifecycleDate: type: object description: > The calendar day a lifecycle action takes effect. Deliberately narrower than [Fmv1Date](/api-reference/object-primitives/date): a lifecycle action records a wall-clock DAY, so there is no `timezone` and no ISO `{ date: "YYYY-MM-DD" }` alternative — send `year`, `month` and `day`. Any other key is ignored. The date must be a real calendar day (`2026-02-31` is rejected) and fall between the years 1900 and 2200. required: - year - month - day properties: year: type: integer minimum: 1900 maximum: 2200 description: Four-digit calendar year (e.g. 2026) month: type: integer minimum: 1 maximum: 12 description: Month, 1-based (1=January, 12=December) day: type: integer minimum: 1 maximum: 31 description: Day of month, 1-based (1-31) 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. ````