Flight Application (Category 04) Rules Web Service

Flight Application (Category 04) Rules API is used to further restrict a fare beyond a specified routing and/or transfer capabilities. The API is designed by ATPCO to meet your needs for automated table creation so you can reduce manual input and get your fares to market faster.

Request

Your request to the Flight Application (Category 04) Rules Web Service must provide a valid OAuth Access Token. For instructions on how to obtain and use an OAuth Access Token programmatically, see OAuth Access Tokens and Authentication. You must also specify parameters in the request body.

Request Header Parameters

See OAuth Access Tokens and Authentication for instructions on header parameters needed for authentication.

Request Body

The request body should be formatted as a JSON object (examples below).

Request Object Parameters

All data requests must be received in the JSON format specified by ATPCO, with field names and sub values found in Data Application unless otherwise specified (fields and sub values (i.e., parameters) detailed below). Field names and provided values must be enclosed in quotation marks (e.g., "tvlDtExp").

• "" or " " as a field name or field value: an empty or non-empty blank string within quotation marks in the request is ignored and will not appear in the JSON response
• Invalid field names in a request are ignored
• Invalid field values in a request generate an error

If your request contains field names that are invalid in a request yet valid in a response (e.g., msgs or msg), those fields will be eliminated during processing and overlaid when necessary in the response.

All String fields (enclosed in double quotes) will have leading and trailing spaces removed unless removing all blanks would violate a possible value for a field where blank(s) is valid on a JSON request. Some fields may have special leading/trailing blanks removal rules such as NoteText996, where only trailing blanks are removed to preserve any intentional text indentations.

Examples of Invalid Field names and values

The request object can include any of the following parameters:

Category 4 Parameters

994 Override Date Fields

986 First Carrier Flight Fields

986 Second Carrier Flight Fields

Loc 1 995 Geographic Specification Fields

Loc 2 995 Geographic Specification Fields

Via 995 Geographic Specification Fields

996 Note Text

General Fields

Response

Responses from the Flight Application (Category 4) Rules Web Service use the same parameters as requests, outlined above. Responses can also include msg and msgs, which are used to communicate error messages.

Example Requests and Responses

Simple Category Request without Carrier Flight Tables

(display only table numbers in response)

{
   "flightApplication04": {
    "flightApplCd": "1"
    "flight1": "1234",
	"carrier1": "XX",
	"flt1ToFlt2RI": "1",
	"flight2": "5678", 
	"carrier2": "XX"
	   }
}

{
   "flightApplication": {
    "tblNum": "4035046"
  }
}

Simple Category Request with Supporting Table 994

(display table numbers in response)

{
    "flightApplication04": {
    "fltApplCd": "1",
	"flight1": "Any",
	"carrier1": "XX",
	     "ovrrdDt994": {
      "rsvEff": "20200315"
    }
  }
}

{
        "flightApplication04": {
        "tblNum": "99000129",
          "ovrrdDt994": {
            "tblNum": "99002126"
        }
    }
}

Request Providing 986 Fields

(display only table numbers in response)

{
 
  "flightApplication04": {
    "fltApplCd": "1",
	"firstCxrFlt986": {
	"firstCxrFlt986Items":[
      {"marketingCarrier": "XX",
      "operatingCarrier": "ZZ",
 	  "flight1":"1500,"
	  "flight2":"1750"
	},
   {"marketingCarrier": "XX",
      "operatingCarrier": "YY",
 	  "flight1":"1500,"
	  "flight2":"1750"
	}
	],
	"flt1ToFlt2RI": "1",
	"flight2": "5678", 
	"carrier2": "DD"
    "loc1mGeoSpec995": {
      "type": "P",
      "loc1": "IAD"
      },
    "loc2GeoSpec995": {
      "type": "P",
      "loc1": "LHR"
      },
    "trvlLocAppl": "1",
    "trvlLocVia": "B",
      "ovrrdDt994": {
      "tvlEff": "20200730",
      "tvlDisc": "20200831",
      "tktEff": "20200730",
      "tktDisc": "20200831",
      "rsvEff": "20200730",
      "rsvDisc": "20200831"
    },
    "noteTxt996": {
      "txtLns": [
        {
          "lnNum": "1",
          "txt": "THIS IS SAMPLE NOTE TEXT"
        },
        {
          "lnNum": "2",
          "txt": "         INDENTATION AND LINE BREAKS"
        },
        {
          "lnNum": "3",
          "txt": "              IN YOUR REQUEST AND RESPONSE."
        },
        {
          "lnNum": "4",
          "txt": "WE HOPE THAT YOU ARE ENJOYING OUR DEMO.."
        }
      ]
    }
  }
}

{
        "flightApplication04": {
        "tblNum": "99000129",
        "loc1GeoSpec995": {
            "tblNum": "99000770"
        },
        "loc2GeoSpec995": {
            "tblNum": "99000771"
        },
        "ovrrdDt994": {
            "tblNum": "99002126"
        },
        "noteTxt996": {
            "tblNum": "99051363"
        }
    }
}

Simple Category Request Using Data and Existing Table Number

(display table number only in response)

  "flightApplication04": {
    "fltApplCd": "1",
	"flight1": "7000",
	"carrier1": "XX",
	"ovrrdDt994": {
            "tblNum": "99002126"
        }
  }
}

{
  
    "flightApplication04": {
        "tblNum": "99000129",
        "ovrrdDt994": {
            "tblNum": "99002126"
        }
       }
    }
}