Day Time (Category 2) Rules Web Service
Day Time (Category 2) Rules API is used to specify the days of the week and/or time of day when travel is or is not permitted. 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 Day Time (Category 2) 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 2 Parameters
Field name | Description | Type | Format | Example |
---|---|---|---|---|
daytime02 |
Wrapper for Category 2 domain | Collection of key-value pairs | { } |
|
dtRangeAppl |
Indicates whether the the day and/or time specified are single day or a range of days | String (max 1-character) | "D" = Day; "R" = Range |
"D" |
startTm |
The first time travel is permitted for a day or range of days | String | 24 hour clock | "0900" |
stopTm |
The last time travel is permitted for a day or a range of days | String | 24 hour clock | "2350" |
notPermitted |
An indicator specifying days and/or times are not permitted for travel | String (max 1-character) | "X" = Not Permitted |
"X" |
dayOfWeekItems |
The day(s) travel is permitted or is not permitted | String | "1" = Monday; "2" = Tuesday; "3" = Wednesday; "4" = Thursday; "5" = Friday; "6" = Saturday; "7" = Sunday |
"["01" ]"= Single Day; "["1","3"]" = Multiple Days |
sameDay |
An indicator specifying return travel must be on the same day of departure | String | "X" = Same Day |
"X" |
occurrence |
The occurrence of the day of week or day/time combination for return travel | String | "01" = First; "02" = Second; "03" = Third; "04" = Fourth; "05" = Fifth; "06" = Sixth |
"03" |
sysAssumOvrrd |
Indicates to overide the system assumption that the data must processed from the commencement of the Pricing Unit. | String | "X" = Override | "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 Day Time (Category 2) 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 with Only Time
(display only table numbers in response)
{
"rtnTblNumsOnly":"Y",
"daytime02": {
"startTm": "0900",
"stopTm": "1000"
}
}
{
"rtnTblNumsOnly": "Y",
"daytime02": {
"tblNum": "4035046"
}
}
Simple Category Request with Supporting Table 994
(display table numbers and values in response)
{
"rtnTblNumsOnly":"N",
"daytime02": {
"dtRangeAppl": "R",
"startTm": "0900",
"stopTm": "1000",
"dayOfWeekItems": ["1","2","3"],
"ovrrdDt994": {
"rsvEff": "20180101"
}
}
}
{
"rtnTblNumsOnly": "N",
"daytime02": {
"tblNum": "4034903",
"dtRangeAppl": "R",
"startTm": "0900",
"stopTm": "1000",
'dayOfWeekItems": ["1","2","3"],
"ovrrdDt994": {
"tblNum": "58696",
"rsvEff": "20180101"
}
}
}
Full Category Request
(display only table numbers in response)
{
"rtnTblNumsOnly":"Y",
"daytime02": {
"dtRangeAppl": "D",
"startTm": "2200",
"stopTm": "2300",
"notPermitted": "X",
"occurrence": "01",
"dayOfWeekItems": ["3"],
"sameDay": "X",
"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"
}
}
}
{
"rtnTblNumsOnly": "Y",
"daytime02": {
"tblNum": "4035073",
"ovrrdDt994": {
"tblNum": "58746"
},
"geoSpec995": {
"tblNum": "274619"
},
"noteTxt996": {
"tblNum": "8187666"
}
}
}
Simple Category Request Using Data and Existing Table Number
(display table number and values in response)
{
"rtnTblNumsOnly":"N",
"daytime02": {
"startTm": "0100",
"stopTm": "0300",
"ovrrdDt994": {
"tblNum": "12345678",
}
}
}
{
"rtnTblNumsOnly": "N",
"daytime02": {
"tblNum": "4034902",
"startTm": "0100",
"stopTm": "0300",
"ovrrdDt994": {
"tblNum": "12345678",
}
}
}