Breaking Changes

Breaking changes are any changes that might require action from our integrators.

remove redirectUrl from the CreateMovieOrderInput object.
Reason: This field needs to be removed as part of the this breaking change.

remove hasCheckoutLink and checkoutUrl from the return fields of createMovieOrder.
Reason: GSC payment page has been removed and need not to be displayed to user.

rename isPackage field of MovieTicket object to hasBundle.
Reason: So that the field name is more descriptive.

Removal of isValid field from MovieShowtime object.
Reason: The system will always return showtimes that are not expired and valid. Hence, this field is unnecessary.
Make externalId argument of CreateMovieOrderCustomerInput optional.
Reason: Some integrator may not pass the the User ID from their DB as it may be sensitive.

Removal of CreatePaymentWithMovieOrder mutation.
Reason: The purpose of this mutation is to create payment record on WeTix side. We realized the payment record can be created when the CreateMovieOrder mutation is called. Hence, to reduce the network call on the integrator side, we have removed this mutation.
languageCode change to languageCodes for Movie and CinemaMovie objects.
Reason: WeTix does not present movies with multiple languages as separate movies, but it is presented as single movie with multiple languages. Hence, a movie may have multiple language codes.

Removal of currencyCode, discountAmount, bookingAmount, totalAmount, selectedTickets, and selectedConcessions from the MovieOrderSession object.
Reason: Our initial intention of having these fields on MovieOrderSession was to persist the selected tickets and concessions before user has created an order, so that when user refereshes our integrator's movie order session page the selected tickets and concessions can still be displayed. However, currently we do not have any API that would allow our integrator to update the movie order session when the user's ticket or concessions selection changes. Hence, we will not be persisting these data on our end and our integrators may persist them on their end. However, these data will be available on the MovieOrder object.

Removal of activeOnly argument from MovieShowtimeConnection argument.
Reason: Our API will always return showtimes that are available or active only, hence this argument is unnecessary.