Reservation management
LSGQL API referenceReservation management

markTravelerAsCheckedIn mutation

This mutation is in the beta-launch phase, and it is still in development. If you are interested in adopting this capability, contact your Technical Account Manager.

Marks a guest as checked in to the reservation. A reservation is designated as checked-in when the property has completed its standard check-in procedure and the traveler has been granted access to the accommodation.

Add this mutation to your existing check-in workflow so that Expedia receives the arrival confirmation in real time. This reduces duplicate work for property staff and enables Expedia to promptly update the reservation’s cancellation eligibility.

Validation rules:

  • A reservation can be marked as checked in only once.
  • If a reservation has already been marked as checked in Expedia Partner Central, it cannot also be marked as checked in using this mutation.
  • A reservation cannot be marked as checked in before the check-in date.
  • After a reservation is marked as checked in, it cannot be reconciled as “cancelled” or “no show”.
  • Guests cannot initiate a cancellation on a booking that has been marked as checked in.
  • Reservations with CONFIRMED and UNCONFIRMED statuses can be marked as checked in. Cancelled reservations (status is CANCELLED) cannot.

Syntax

1mutation {
2 markTravelerAsCheckedIn(
5}

Example

1mutation {
2 markTravelerAsCheckedIn(
3 input: {
4 propertyId: "123",
5 clientMutationId: "xyz",
6 reservationId: "321",
7 }
8 ) {
9 clientMutationId
10 reservationId
11 }
12}

Arguments

NameDescription

input

Required.

Property and reservation IDs.

Type: MarkTravelerAsCheckedInInput

Types


Name
Type
ID
ID

The ID scalar type represents a unique identifier, often used to refetch an object or as key for a cache. The ID type appears in a JSON response as a String; however, it is not intended to be human-readable. When expected as an input type, any string (such as "4") or integer (such as 4) input value will be accepted as an ID.

MarkTravelerAsCheckedInInput
InputObject

Input arguments to the markTravelerAsCheckedIn mutation.

FieldDescription
clientMutationId

Partner's transaction ID that uniquely identifies the request, which can be used to associate requests and responses for troubleshooting purposes. This ID must be unique across requests and cannot be reused. However, if a request needs to be retried, such as because it failed or timed out, the ID provided in the original request should be used. The ID can be in any format as long as it uniquely identifies the request.

Type: String
propertyIdNot nullable.

Expedia ID of the property whose reservation will be marked as checked in.

Type: ID
reservationIdNot nullable.

Expedia ID of the reservation that will be marked as checked in.

Type: ID
MarkTravelerAsCheckedInPayload
Object

Payload of the markTravelerAsCheckedIn mutation.

FieldDescription
clientMutationId

Partner's transaction ID that identifies the request, which can be used to correlate with partner's transaction logs. This ID must be unique across requests and cannot be reused.

Type: String
reservationId

Expedia ID of the reservation that was marked as checked in.

Type: ID
String
String

The String scalar type represents textual data, represented as UTF-8 character sequences. The String type is most often used by GraphQL to represent free-form human-readable text.