> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axisdata.net/llms.txt
> Use this file to discover all available pages before exploring further.

# OTA_ProductDescriptiveInfoRQ

The `OTA_ProductDescriptiveInfoRQ` (Excursion Details Request) is used to request NBC mapping data for a specific excursion. It follows the OTA schema and is the entry point in the transactional model to retrieve descriptive data for excursions.

<Tip>Already know OTA messages? Jump straight into testing.</Tip>

<Card title="OTA_TourActivityBookRQ API call" icon="image" href="/api-reference/endpoint/excursion/nbc" arrow="true" horizontal>
  Try our API playground in real time.
</Card>

## Purpose

This request fetches descriptive information for excursions needed for NBC mapping, by referencing a specific `TourActivityID`. It is analogous in intent to product descriptive requests in other verticals, but targeted at excursions.

## Structure – Root Element

```xml theme={null}
<OTA_ProductDescriptiveInfoRQ>
```

**Key Attributes:**

* `Version`: Specification version (e.g., "2016.2").
* `PrimaryLangID`: Primary language code (ISO 639).
* `AltLangID`: Alternate language code (ISO 639).
* `SequenceNmbr`: Client-assigned sequence number for idempotence/tracking.
* `xmlns`: "[http://www.opentravel.org/OTA/2003/05](http://www.opentravel.org/OTA/2003/05)".

## Structure – Core Elements

### POS (Point of Sale)

Identifies the requesting party and contains credentials.

```xml theme={null}
<POS>
  <Source>
    <RequestorID ID="TEST" ID_Context="AxisData" Type="22"/>
  </Source>
  <Source>
    <RequestorID Type="88" ID="TEST" MessagePassword="testpass"/>
  </Source>
</POS>
```

### ProductDescriptiveInfos / TourActivityDescriptiveInfo

Container specifying which excursion to describe.

* `TourActivityDescriptiveInfo/@TourActivityID` — **required**. Identifies the excursion to be described.

```xml theme={null}
<ProductDescriptiveInfos>
  <TourActivityDescriptiveInfo TourActivityID="XESPMI5L4U"/>
</ProductDescriptiveInfos>
```

## Complete Example

```xml theme={null}
<OTA_ProductDescriptiveInfoRQ xmlns="http://www.opentravel.org/OTA/2003/05" Version="2016.2" PrimaryLangID="EN" AltLangID="EN" SequenceNmbr="1">
  <POS>
    <Source>
      <RequestorID ID="TEST" ID_Context="AxisData" Type="22"/>
    </Source>
    <Source>
      <RequestorID Type="88" ID="TEST" MessagePassword="testpass"/>
    </Source>
  </POS>
  <ProductDescriptiveInfos>
    <TourActivityDescriptiveInfo TourActivityID="XESPMI5L4U"/>
  </ProductDescriptiveInfos>
</OTA_ProductDescriptiveInfoRQ>
```

## Common Use Cases

* **Excursion Details Request (NBC mapping):** Request descriptive data for a single excursion by `TourActivityID` to drive mapping of products/services.

## Playground

<Card title="OTA_TourActivityBookRQ API call" icon="image" href="/api-reference/endpoint/excursion/nbc" arrow="true" horizontal>
  Try our API playground in real time.
</Card>

<Tip>Use the desired request in the playground and receive responses from our test environment API!  </Tip>