Documentation of the CarRentalAgentService

BookingType Enumeration

Enumeration of possible types for a reservation. CreateReservationV2

public enum BookingType

Remarks

The BookingType of a Reservation specifies, the customer that is stored as payee of commission and the customer that is liable for payment.

Members

Member Name Description
Undefined Undefined enum value, for internal use. This is no valid setting when accessing the web service.
Agency Specifies that the reservation should be handeled as "Agenturinkasso". Therefore no Customer-Data is needed within the CreateReservationV2Request. Billing for this booking will be done between SunnyCars and the booking agency. There are two possibilities to create a reservation of type "Agency". The first possibility to perform a reservation of this type, is to use a Ticket that was created for a valid Agency-Account as OperatorKey by performing a TicketGrantingTicketRequest. The second possibilility is to use a Ticket that was created for a valid Agency-Account as OperatorKey and another valid Agency-Account as ImpersonationKey by performing a TicketGrantingTicketRequest. Thereby the Agency handed over as OperatorKey acts as the middleman between SunnyCars and the Angency handed over as ImpersonationKey. Billing for this booking will be done between SunnyCars and the Angency handed over as ImpersonationKey.
Direct Specifies that the reservation should be handeled as "Direktinkasso". Billing for this booking will be done directly between SunnyCars and the end-customer. There are two possibilities to create a reservation of type "Direct". The first possibility to perform a reservation of this type, is to create a Ticket for a valid Agency-Account as OperatorKey by performing a TicketGrantingTicketRequest. The data of the end-customer(liable for payment) has to be handed over in the customer data properties of CreateReservationV2Request. The second possibility to create a reservation of type "Direct" is to create a Ticket for a valid Agency-Account as OperatorKey and a valid(registered) end-customer account as ImpersonationKey. Thereby the second possibility is applicable by internal applications of sunnycars only.
DirectLink Specifies that the reservation should be handeled as "DirectLink"-reservation. Billing for this booking will be done directly between SunnyCars and the end-customer. To perform a reservation of this type, a Ticket for a valid Affiliate-Account as OperatorKey and a valid(registered) end-customer account as ImpersonationKey has to be created by performing a TicketGrantingTicketRequest. Thereby reservations of type "DirektLink" are applicable by internal applications of sunnycars only.
Broker Specifies that the reservation should be handeled as "Broker"-reservation. To perform a reservation of this type, a Ticket for a valid Broker-Account as OperatorKey and a valid(registered) Agency account as AgencyKey has to be created by performing a BrokerTicketGrantingTicketRequest. Thereby the Broker handed over as OperatorKey acts as the middleman between SunnyCars and the Angency handed over as ImpersonationKey. Billing for this booking will be done between SunnyCars and the Broker handed over as OperatorKey.

Requirements

Namespace: SunnyCars.Schema.Osi.WsReservation.V4

Assembly: Sunnycars.Schema.Osi.WsReservation.V4 (in Sunnycars.Schema.Osi.WsReservation.V4.dll)

See Also

SunnyCars.Schema.Osi.WsReservation.V4 Namespace | Reservation | CreateReservationV2