Definitions
The Architect APIs are built around a set of core concepts that define how pricing decisions are structured and managed. This page provides clear definitions of those concepts so you can better understand how to interact with blueprints and conditions using the API.
Blueprint
A blueprint is the primary organizational resource in the Architect system. It represents a named collection of pricing rules (conditions) that define how fares should be evaluated and modified for a host carrier.
Each blueprint includes:
- A unique identifier (
id) - A human-readable name
- A type classification
- Metadata about creation
Blueprints serve as containers for conditions to apply on a search scope and are the top-level resource when working with Decision Support workflows.
Blueprint Type
The blueprint type classifies the kind of pricing logic a blueprint contains.
| Value | Description |
|---|---|
General | Standard blueprint for general fare pricing rules |
Historic | Blueprint used for historical fare analysis |
Web | Blueprint for web fare pricing rules |
Condition
A condition is a pricing rule within a blueprint. It defines a set of match criteria and corresponding actions (apply logic) that determine how fares are evaluated and modified.
Each condition includes:
- A unique identifier (
id) - A descriptive name
- Content consisting of one or more rows of match/apply logic
- Metadata about creation and last update
Condition Row
A condition row represents a single rule within a condition. Each row consists of two parts:
| Component | Description |
|---|---|
| Match | Defines the criteria used to identify which fares the rule applies to |
| Apply | Defines the action to take on fares that match the criteria |
Match Criteria
The match section of a condition row defines the scope of fares that the rule targets. Match criteria are organized into several categories:
Scope Data
Scope data refers to fares returned in the blueprint search. These may be fares being changed, or fares used as the basis for changes, cancellations, or creation of other fares.
Key scope data fields include:
| Field | Description |
|---|---|
productType | Product classification (PUB, PVT, CNP, CNV, WEB) |
origin | Fare record's origin city or airport |
destination | Fare record's destination city or airport |
carrier | Carrier associated with the fare record |
fareClass | Fare class or basis code |
market | Origin-destination market pair |
fareAmount | Fare amount value |
currency | Currency code |
passengerType | Passenger type code (e.g., ADT) |
sellableStatus | Sellable status of the fare (Active, Limited, etc.) |
📝 Wildcards (
^,%,_,#) can be used in many scope data fields. The+prefix denotes a city or country group reference. For detailed wildcards available, see the scope data specification.
New Data
New data fields define criteria based on newly filed fare information, typically used when evaluating changes.
Market Parameters
Market parameters provide additional market-level context for fare evaluation, such as market type and first sell-up date.
Brands
Brand-related criteria for fare evaluation, including tariff and carry-on allowance information.
Web Fare Parameters
Parameters specific to web fare evaluation, including web Reservation Booking Designator (RBD) and discount values. Only applicable to blueprints of type Web.
Apply Actions
The apply section of a condition row defines what action to take on matched fares.
| Field | Description |
|---|---|
actionCode | The action to perform: Modify, Cancel, or Create |
tariffNumber | Tariff number for the resulting fare |
carrier | Carrier code for the resulting fare |
footnote | Footnote designation |
fareAmount | Fare amount (supports expressions like $OneWayAMT+20) |
currency | Currency code |
origin | Origin for the resulting fare |
destination | Destination for the resulting fare |
cabin | Cabin class (Economy, Business, etc.) |
rounding | Rounding direction (Up, Down) |
unit | Rounding unit precision |
Subscription Times
Subscription times represent the scheduled processing times for domestic and international fare data. These times indicate when ATPCO processes fare submissions for each market type.
The Subscriptions Times API returns these values in two formats:
- ISO 8601 — Human-readable UTC date-time (e.g.,
2025-01-01T18:00:00Z) - Epoch — Millisecond timestamp for programmatic use (e.g.,
1735711200000)
Host Carrier
A host carrier is the airline whose fare data is being managed through the Architect system. API access is scoped to the host carrier associated with the authenticated credentials. All blueprint and condition operations are performed within the context of the authenticated host carrier.
Authorization Scopes
Your client credentials are configured with the needed scope to access the APIs. The appropriate scopes are assigned during onboarding—you do not need to request or manage them separately.