| Associate | The concept of associate is used in the context of data and work units.
- Data: Products and bundles are separate data types in Product Catalog. Creating a reference between them is known as associating them.
- Products: In addition to being offered individually as a “standalone,” a product can be offered as part of one or more bundles. This is done by associating the product with the bundle(s).
- Bundles: Intake bundles must have at least two associated products, although auto-populate bundles sometimes have no products.
- Work units: In Product Catalog, every data change (create, update, discontinue) must be associated with a work unit. This association is made at the time the data change is processed.
|
| Auto-populated data | - As part of the onboarding process, airlines have the option to authorize ATPCO to populate their catalog with data from one or more ATPCO source systems: Fares, Rules, Optional Services, Branded Fares, Routehappy Attributes.
- Auto-populated data is not required to create a catalog, but it provides seed data that can facilitate adoption.
- The auto-populate process runs on an hourly basis every day of the week
|
| Blank spaces and empty strings | - Blank spaces and empty strings are not valid values.
- In an API request, an element with a blank space or empty string removes any existing value from the element.
|
| Cancel | See Discontinue |
| Create | The concept of create can be defined as:
- Adding a product or bundle to Product Catalog by the Intake API
- Auto-populating data from ATPCO source system process and transforming the data to products and bundles
- Generating a work unit.
|
| Delete | See Discontinue |
| Disassociate | The concept of disassociate means the opposite of associate with data and work units.
- Data: Removing the reference between a product and its associated bundle. These data types remain in Product Catalog, but they are no longer referenced to one another.
- Work units: Removing the reference between a work unit and product or bundle.
|
| Discontinue | Discontinuing data removes it from the Product Catalog database. The removal is effective when the data’s associated work unit is released.
Discontinued data is purged from the ATPCO system seven days after the discontinue data. |
| Element | An element represents a characteristic, or attribute, of a product or bundle. Here are two examples:
- Legroom and angle are characteristics (elements) of seat products.
- Legroom can be described as less, more, or standard
- Angle can be described as angle flat, full flat, or not flat
- Weight and size are characteristics (elements) of baggage products
- Weight has maximum and minimum measurements in kilograms or pounds
- Size has maximum and minimum measurements in centimeters or inches
A product or bundle displays only those elements that exist for it. For example:
- Suppose a seat product in Routehappy Attributes has legroom standard but no width, pitch, or angle measurements.
- The auto-populated seat product in Product Catalog shows the legroom element but no other elements
|
| Equipment ID source | Equipment in Product Catalog has an indicator that identifies the source of the data as either:
- Bilaterally defined by the Catalog owner and Catalog receiver/user
Equipment ID source = X
or- Defined in ATPCO Appendix F (Equipment codes)Equipment ID source = A
Product Catalog supports both data sources but can validate only those that have equipment ID source A. |
| Intake data | Intake data refers to data that is created, updated, and discontinued from Product Catalog by catalog owners and their authorized tech providers by means of an API request. |
| Location source | Locations in Product Catalog have a code that identifies the source of the data.
- Locations with a code value X are bilaterally defined by the catalog owner and other organizations.
or- Locations with a code value I are industry-defined geography codes that are published by ATPCO
Product Catalog supports both data sources but can validate only those that have location source I. |
| Passenger type source | Passenger types in Product Catalog have an indicator that identifies the source of the data as either:
- Bilaterally defined by the Catalog owner and Catalog receiver/user
Passenger type source = X
or- Defined in ATPCO Appendix A (Passenger Type Codes)
Location source = A
Product Catalog supports both data sources but can validate only those that have passenger type A. |
| Reassociate | The process of moving one or more (products and/or bundles) out of the work unit they currently belong to (the source work unit) and into a different work unit (the target work unit), in a single operation. |
| Remove | See Discontinue |
| RESTful practices relaxed | Product Catalog APIs are grounded in RESTful principles, but certain best practices are intentionally relaxed to accommodate real-world needs.
- PATCH is used for partial updates and when data retrieval or deletion requires complex or large payloads, such as filters and bulk operations.
Using PATCH for these purposes improves efficiency and avoids the overwriting of unchanged data. - POST is sometimes used instead of GET or DELETE.
Although using POST in this manner diverges from strict REST conventions, it provides practical benefits such as avoiding URL length limitations and securely transmitting sensitive criteria in the request body.
|
| Retrieve | The process by which products, bundles, and work units are fetched from the Product Catalog database by means of a Retrieve, or GET, API request. |
| Subscriber | A subscriber is any company that receives automated data from ATPCO. In the context of Product Catalog, subscribers consist of the catalog owner and its authorized technology partners. |
| Update | The process by which a product, bundle, or work unit is changed. Examples of update actions include the following
- Adding, changing, or removing product or bundle elements
- Adding, removing, or replacing product or bundle rules sets
- Adding or removing references between products and bundles
- Changing a work unit’s name or description
|
| Work unit | A work unit is a tool for grouping multiple products and bundles together so that they can be distributed at the same time. |