Skip to main content
The OTA_TourActivityBookRS (Excursion Book Response) confirms a quote or a committed booking for a tour/activity service. It returns confirmation details such as service identifiers, participant data, pricing, partner/internal references, cancellation rules, and (optionally) QR codes.

Purpose

  • Quote: Confirms availability and final price without creating a reservation (no commitment).
  • Commit: Creates a binding booking in the reservation system; penalties may apply to changes/cancellations.
  • If the booking cannot be processed, the response omits <Success/> and returns error details under <Errors/>. Error Scenarios

Structure – Root Element

Key attributes
  • Version: OTA spec version (e.g., 2008.1).
  • xmlns: http://www.opentravel.org/OTA/2003/05.

Structure – Core Elements

BasicInfo

Confirms the booked service identifiers returned from search/detail.

Location

Optional region/location context for the service.

ParticipantInfo

Echoes each participant’s age at the time of service, a unique ParticipantID, and the age qualifier code (QualifierInfo) following OTA AQC conventions (e.g., 10 adult, 8 child).

Pricing

Final confirmed amounts appear under Pricing. Values in Summary are final for accountancy. Group size (when relevant) is returned as KnownGroupsize.

Extras

Extras confirmed in the booking appear in the response; their amounts are already included in the total charge.

TPA_Extensions

Includes general information returned by the provider.

References

Partner and AxisData internal references are returned as UniqueID entries. Use client references for vouchers and communications; both client and internal references support cancellation. Master (Type=36) and child (Type=37) references are provided.

CancelPenalties

Cancellation policy is returned for both Quote and Commit responses. Use child references for partial cancellations.

QR Codes

Some providers return tickets/QR codes via UniqueID Type="30" under TPA_Extensions:
  • Direct QR value: ID contains the QR string to render as a code.
  • QR URL: ID contains a URL to download the QR/ticket.

BookingStatus

When present, booking status may also be returned as a TPA element:

Complete Examples

Best Practices

  1. Use client references for external communications (voucher/finance), but retain internal references for support and cancellations.
  2. Provide accurate ages at service date with correct OTA AQC codes in ParticipantInfo.
  3. Read CancelPenalties for both quotes and commits; use child references to scope partial cancellations.