Seasonality (Category 3) Rules Web Service
Seasonality (Category 3) Rules API is used to restrict a fare to a specific date or range of dates. 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 Seasonality (Category 3) 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.
Field name | Value | Issue | System Handling |
---|---|---|---|
" tvlDtExp" |
Extra leading space | ignored | |
"tvlDtExp " |
Extra trailing space | ignored | |
"tvlDExp" |
Field name incorrect. Missing 't' | ignored | |
" WAS" |
Extra leading space | Error invalid city format |
Examples of Invalid Field names and values
The request object can include any of the following parameters:
Category 3 Parameters
Field name | Description | Type | Format | Example |
---|---|---|---|---|
seasonality03 |
Wrapper for Category 3 domain | Collection of key-value pairs | { } |
|
startDt |
The first date or the first date in a for a range of dates travel is permitted | String | "YYYYMMDD" = Fulldate; "MMDD" = Month Day with no year; "MM" = Month; "YYYYMM" = Month and Year with no date | "20180930" |
stopDt |
The last Date travel may commence from the origin of the pricing unit | String | YYYYMMDD | "20180930" |
seasPromo |
Indicates whether teh dates specified are seasonal or promotional | String (max 1-character) | "X" = Season; "D" = Display Promotion |
|
sysAssumOvrrd |
Indicates to overide the system assumption that the dates apply to Pricing Unit. When overridden dates apply to each trip | String | "X" |
994 Override Date Fields
Field name | Description | Type | Format | Example |
---|---|---|---|---|
ovrrdDt994 |
Wrapper for 994 Subdomain | Collection of key-value pairs | { } |
|
tvlEff |
The first date travel is valid for the Category Record 3 provisions | String | YYYYMMDD | "20180930" |
tvlDisc |
The last date travel is valid for the Category Record 3 provisions | String | YYYYMMDD | "20180930" |
tktEff |
The first date ticketing is valid for the Category Record 3 provisions | String | YYYYMMDD | "20180930" |
tktDisc |
The last date ticketing is valid for the Category Record 3 provisions | String | YYYYMMDD | "20180930" |
rsvEff |
The first date reservations can be made for the Category Record 3 provisions | String | YYYYMMDD | "20180930" |
rsvDisc |
The last date reservations can be made for the Category Record 3 provisions | String | YYYYMMDD | "20180930" |
995 Geographic Specification Fields
Field name | Description | Type | Format | Example |
---|---|---|---|---|
geoSpec995 |
Wrapper for 995 Subdomain | Collection of key-value pairs | { } |
|
type |
Indicates the type of geographic specified for the location or TSI for the Category Record 3 provisions | String (max 1-character) | "A" = Area; "Z" = Iata Zone ; "S" = State ;"C" = City ;"P" = Airport ;"N" = Nation |
|
loc1 |
The first specified location valid for the Category Record 3 provisions | String max (5-character) | "1" = one digit numeric Area designator; "210" = 3 digit numeric assigned Iata Zone ; "FL US" = 5 digit including a space ;"NYC" = 3 digit alpha City code ;"EWR" = 3 digit alpha Airport code ;"US" = 2 digit alpha Iata Nation/Country code |
|
loc2 |
The last specified location valid for the Category Record 3 provisions | String max 5- (character) | "1" = one digit numeric Area designator; "210" = 3 digit numeric assigned Iata Zone ; "FL US" = 5 digit including a space ;"NYC" = 3 digit alpha City code ;"EWR" = 3 digit alpha Airport code ;"US" = 2 digit alpha Iata Nation/Country code |
|
tsi |
Travel Segment Indiator valid for the Record 3 provisions | String max 2 -(character) | "03" = 2 digit numeric TSI as defined |
996 Note Text
Field name | Description | Type | Format | Example |
---|---|---|---|---|
noteTxt996 |
Wrapper for 996 Table | Collection of key-value pairs | { } |
|
txtLns |
Collection of lines of free-form text specified in the request | Array of collections of key-value pairs | [ { "lnNum": "1", "txt": "THIS IS SAMPLE NOTE TEXT" }, ... ] |
|
lnNum |
Line number indicating the placement of the associated txt field |
String | # | "1" |
txt |
The text to be printed at the corresponding lnNum (line number) |
String | Free-form text | "THIS IS SAMPLE NOTE TEXT" |
General Fields
Field name | Description | Type | Format | Example |
---|---|---|---|---|
rtnTblNumsOnly |
Indicates whether to display the created table numbers and the data values specified in the Request. When set to "Y" (True), ONLY the table numbers will display in the Response. Default is "N" (False). |
String (max 1-character) | "Y" = True; "N" = False |
"N" |
tblNum |
Indicates an existing 900 series table in a request or generated in a response when data has been created | String | ##### | "4035046" |
Response
Responses from the Seasonality (Category 3) 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 Full Date Category Request
{
"seasonality03": {
"startDt": "20180930",
"stopDt": "20181030",
"seasPromo": "X"
}
}
{
"rtnTblNumsOnly": "Y",
"seasonality03": {
"tblNum": "4035046"
}
}
Simple Request with No Year with Supporting Table 994
{
"seasonality03": {
"startDt": "1001",
"stopDt": "1030",
"seasPromo": "X",
"ovrrdDt994": {
"rsvEff": "20200915"
}
}
}
{
"seasonality03": {
"tblNum": "4034902",
"ovrrdDt994": {
"tblNum": "58696"
}
}
}
Simple Request with only Month with Supporting Table 994
{
"seasonality03": {
"startDt": "10",
"stopDt": "10",
"seasPromo": "X",
"ovrrdDt994": {
"rsvEff": "20200915"
}
}
}
{
"seasonality03": {
"tblNum": "4034902",
"ovrrdDt994": {
"tblNum": "58696"
}
}
}
Full Category Request
(display only table numbers in response)
{
"seasonality03": {
"startDt": "20180201",
"stopDt": "20181030",
"seasPromo": "D",
"sysAssumOvrrd": "X",
"ovrrdDt994": {
"rsvEff": "20180101",
"rsvDisc": "20180731",
"tktDisc": "20180731",
"tvlEff": "20180201",
"tvlDisc": "20181030"
},
"noteTxt996": {
"txtLns": [{"lnNum":"1","txt": "THIS IS SAMPLE NOTE TEXT TO ILLUSTRATE"}
,{"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.."}]
},
"geoSpec995": {
"loc1": "SEA",
"type": "C",
"loc2": "MAD",
"tsi": "01"
}
}
}
{
"seasonality03": {
"tblNum": "4035073",
"ovrrdDt994": {
"tblNum": "58746"
},
"geoSpec995": {
"tblNum": "274619"
},
"noteTxt996": {
"tblNum": "8187666"
}
}
}
Simple Category Request Month and Year Date Format with Existing 994 Table Number
{
"seasonality03": {
"startDt": "202010",
"stopDt": "202010",
"seasPromo": "X",
"ovrrdDt994": {
"tblNum": "12345678"
}
}
}
{
"seasonality03": {
"tblNum": "4034902",
"ovrrdDt994": {
"tblNum": "12345678",
}
}
}