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
- Request
- Response - Success
- Response - Error
1mutation {2 markTravelerAsCheckedIn(3 input: {4 propertyId: "123",5 clientMutationId: "xyz",6 reservationId: "321",7 }8 ) {9 clientMutationId10 reservationId11 }12}
Arguments
| Name | Description |
|---|---|
| Required. Property and reservation IDs. Type: MarkTravelerAsCheckedInInput |
Types
Name | Type | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
ID | ID | |||||||||
The | ||||||||||
MarkTravelerAsCheckedInInput | InputObject | |||||||||
Input arguments to the
| ||||||||||
MarkTravelerAsCheckedInPayload | Object | |||||||||
Payload of the
| ||||||||||
String | String | |||||||||
The | ||||||||||