In each extension point that contains Credit Card data, number and security code are masked. Credit card number is masked except last 4 digits, security code (CVV/CVC) is fully masked. Additionally, these fields contains masking identifier at the end of each separated by the pipe operator "|", e.g.:

If the extension allows to modify Credit Card data, new entered value should not contain a pipe separator and identifier.

This extension point is executed before air segment book request is sent.

It is triggered from graphical path:

This extension point is used by some of the agencies to analyze sales decision factors in the booking process. To take advantage of it, the agency needs to decorate Sabre’s air shopping response with its own tags (or use Sabre-generated tags), then at the time of booking ("Sell & Save Price") Red App may read such data in the extension point to be further stored and analyzed by the agency management.

This extension point is executed after air segment book response is received.

Trigger points are described for dynamo.air.airbooking:beforeAirBookAndPrice.

This extension point is executed before price quote creation request is sent.

It is triggered:

This extension point is executed after price quote creation response is received.

Trigger points are described for dynamo.air.pq:beforePriceQuoteCreation.

This extension point is executed before pricing request is sent.

It is triggered:

This extension point is executed after pricing response is received.

Trigger points are described for dynamo.air.pricing:beforePricing.

This extension point is executed before air availability request is sent.

It is triggered:

This extension point is executed after segment or segments book request is received.

It is triggered:

This extension point is executed before air shopping request is sent.

It is triggered from graphical path:

This extension point is executed after air shopping response is received.

Trigger points are described for dynamo.airshopping:beforeAirShopping.

This extension point is executed before user sees the "Flights" form.

It is triggered from graphical path:

This extension point is executed before user sees the "Air Shopping" form.

It is triggered from graphical path:

This extension point is executed before user sees the "Car Book" form.

It is triggered from graphical path:

This extension point is executed before car book request is sent.

It is triggered from graphical path:

This extension point is executed after car book response is received.

Trigger points are described for dynamo.car:beforeCarBook.

This extension point is executed before user sees the "Car Reservation" form.

It is triggered from graphical path:

This extension point is executed before car shopping request is sent.

It is triggered from graphical path:

This extension point is executed before user sees the exchange comparison form modal (launched during the ticket exchange procedure).

It is triggered from graphical path:

This extension point is executed after exchange comparison response is received.

Trigger points are described for dynamo.exchange:beforeExchangeComparison.

This extension point is executed before user sees the exchange confirmation form modal (launched during the ticket exchange procedure).

It is triggered from graphical path:

This extension point is executed after exchange confirmation response is received.

Trigger points are described for dynamo.exchange:beforeExchangeConfirmation.

This extension point is executed before user sees the "Hotel reservation" form.

It is triggered:

This extension point is executed before the hotel sell (book) request is sent.

It is triggered by submitting the "Hotel reservation" form. How to open "Hotel reservation" form is described for dynamo.hotel.book:beforeHotelBookInput extension point.

This extension point is executed after the hotel sell (book) response is received.

Trigger points are described for dynamo.hotel.book:beforeHotelBook.

This extension point is executed before the hotel details request is sent.

It is triggered:

This extension point is executed after the hotel details response is received.

Trigger points are described for dynamo.hotel.details:beforeHotelDetail.

This extension point is executed before user sees the hotel change dates form.

It is triggered from graphical path using "Change dates" action for the hotel segment. This action can be accessed:

Some of the properties available in the data model are read-only (HotelName, PropertyId, and SegmentNumber).

This extension point is executed before user sees the hotel modify details form.

It is triggered from graphical path using "Modify details" action for the hotel segment. This action can be accessed:

This extension point is executed after hotel segment details modification response is received.

It is triggered:

This extension point is deprecated and will be removed soon.
Use dynamo.hotel.modify:afterHotelModifyDetails extension point instead.

This extension point is executed before hotel shopping request is sent.

It is triggered:

This extension point is executed after hotel shopping response is received.

Trigger points are described in dynamo.hotel.shopping:beforeHotelShopping.

This extension point is executed before user sees the "Create order" form modal.

It is triggered from graphical path:

This extension point is executed before create order modal request is sent (after submitting "Create order" modal in graphical flow when working with an NDC segment).

It is triggered from graphical path:

This extension point is executed after create order modal response is received (after submitting "Create order" modal in graphical flow when working with an NDC segment).

Trigger points are described for dynamo.ndc:beforeOrderCreate.

This extension point is executed before user sees "Advanced pricing" modal form.

It is triggered form graphical path:

This extension point is executed before PNR ignore request is sent.

It is triggered:

This extension point is executed after PNR ignore response is received.

Trigger points are described for dynamo.pnr:beforeIgnore.

This extension point is executed before invoice issue request is sent.

It is triggered from commands starting with DIN (e.g. DIN, DIN/X|S1).

This extension point is executed after invoice issue response is received.

Trigger points are described for dynamo.pnr:beforeInvoiceIssue.

This extension point is executed before end PNR request is sent.

It is triggered:

This extension point is executed after receiving PNR end response.

Trigger points are described for dynamo.pnr.end:beforeEndCommand.

This extension point is executed before request to place a PNR on the queue is sent.

It is triggered:

This extension point is executed after PNR queue place response is received.

Trigger points are described for dynamo.queue.place:beforeQueuePlace.

This extension point is executed before add passive air segment request is sent.

It is triggered:

This extension point is executed after add passive air segment response is received.

Trigger points are described for dynamo.segment:beforeAirPassiveAdd.

This extension point is executed before add passive car segment request is sent.

It is triggered from graphical path:

This extension point is executed after add passive car segment response is received.

Trigger points are described for dynamo.segment:beforeCarPassiveAdd.

This extension point is executed before add passive hotel segment request is sent.

It is triggered:

This extension point is executed after add passive hotel segment response is received.

Trigger points are described for dynamo.segment:beforeHotelPassiveAdd.

This extension point is executed before add other passive segment request is sent.

It is triggered:

This extension point is executed after add passive other segment response is received.

Trigger points are described for dynamo.segment:beforeOtherPassiveAdd.

This extension point is executed before issue miscellaneous intelligent service fee request is sent.

It is triggered from commands starting with MISF (e.g. MISF¥S*AIR AND HOTEL SERVICE FEE¥C*IBM997YYZ).

This extension point is executed after issue miscellaneous intelligent service fee response is received.

Trigger points are described for dynamo.segment:beforeIssueServiceFee.

This extension point is executed before delete segment request is sent.

It is triggered:

This extension point is executed after cancel segment response is received.

Trigger points are described for dynamo.segment.cancel:beforeSegmentCancel.

This extension point is executed before cancel document refund request is sent.

It is triggered from commands starting with WTRX (e.g. WTRX0161234567890).

This extension point is executed after cancel document refund response is received.

Trigger points are described for dynamo.ticketing:beforeCancelDocumentRefund.

This extension point is executed before user sees the "Issue ticket/EMD" form modal.

It is triggered from graphical path:

This extension point is executed before issue ticket request is sent.

It is triggered:

This extension point is executed after issue ticket response is received.

Trigger points are described for dynamo.ticketing:beforeIssueTicket.

This extension point is executed before revalidate ticket request is sent.

It is triggered from commands starting with WETRL/ (e.g. WETRL/S3/C3*21JUN1522JUN15).

This extension point is executed after revalidate ticket response is received.

Trigger points are described for dynamo.ticketing:beforeRevalidateTicket.

This extension point is executed before void document (ticket or EMD) request is sent.

It is triggered:

This extension point is executed after void document (ticket or EMD) response is received.

Trigger points are described for dynamo.ticketing:beforeVoidDocument.