# Updates the BookingOrderItemTicket resource.

Updates the BookingOrderItemTicket resource.

Endpoint: PATCH /v1/booking/orders/{orderId}/items/{orderItemId}/tickets/{id}
Version: 1.0.7
Security: JWT

## Path parameters:

  - `orderId` (string, required)
    Order identifier

  - `orderItemId` (string, required)
    Order item identifier

  - `id` (string, required)
    ticket identifier

## Request fields (application/merge-patch+json):

  - `beneficiary` (object)

  - `beneficiary.firstname` (string, required)
    Example: "john"

  - `beneficiary.lastname` (string, required)
    Example: "doe"

  - `beneficiary.title` (string,null)
    Enum: "mr", "mrs", "mx"

  - `beneficiary.nationality` (string,null)
    Example: "FR"

  - `beneficiary.dateOfBirth` (string,null)
    Example: "2000-01-01"

  - `beneficiary.placeOfBirth` (string,null)

  - `beneficiary.email` (string,null)

  - `beneficiary.phone` (string,null)

## Response 200 fields (application/ld+json):

  - `@context` (any)

  - `@id` (string)

  - `@type` (string)

  - `id` (string)
    Example: "0194cb22-b891-754c-8c4c-777b93f8d072"

  - `voucher` (string,null)

  - `occursAt` (string,null)
    Example: "2025-02-27T15:15:20+00:00"

  - `event` (string,null)

  - `requiredBeneficiaryFields` (array)
    Example: ["firstname","lastname"]

  - `beneficiary` (any)

  - `beneficiaryDesignationDeadline` (string,null)

  - `beneficiaryAmendable` (boolean)

  - `status` (string)
    Enum: "waiting_beneficiary_data", "validated"

  - `seating` (any)

## Response 400 fields (application/ld+json):

  - `@context` (any)

  - `@id` (string)

  - `@type` (string)

  - `title` (string,null)
    A short, human-readable summary of the problem.

  - `detail` (string,null)
    A human-readable explanation specific to this occurrence of the problem.

  - `status` (number)

  - `instance` (string,null)
    A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.

  - `type` (string)
    A URI reference that identifies the problem type

  - `description` (string,null)

## Response 403 fields (application/ld+json):

  - `@context` (any)

  - `@id` (string)

  - `@type` (string)

  - `title` (string,null)
    A short, human-readable summary of the problem.

  - `detail` (string,null)
    A human-readable explanation specific to this occurrence of the problem.

  - `status` (number)

  - `instance` (string,null)
    A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.

  - `type` (string)
    A URI reference that identifies the problem type

  - `description` (string,null)

## Response 404 fields (application/ld+json):

  - `@context` (any)

  - `@id` (string)

  - `@type` (string)

  - `title` (string,null)
    A short, human-readable summary of the problem.

  - `detail` (string,null)
    A human-readable explanation specific to this occurrence of the problem.

  - `status` (number)

  - `instance` (string,null)
    A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.

  - `type` (string)
    A URI reference that identifies the problem type

  - `description` (string,null)

## Response 422 fields (application/ld+json):

  - `@context` (any)

  - `@id` (string)

  - `@type` (string)

  - `status` (integer)
    Example: 422

  - `violations` (array)

  - `violations.propertyPath` (string)
    The property path of the violation

  - `violations.message` (string)
    The message associated with the violation

  - `detail` (string)

  - `description` (string)

  - `type` (string)

  - `title` (string,null)

  - `instance` (string,null)