Retrieve Upload Errors Service


Use the Retrieve Upload Errors Service to interface with ATPCO systems to get a list of errors and/or warnings. This service uses GET HTTP Request method. This service is available to retrieve errors and/or warnings for Fares Upload, Rules Upload, and/or Footnote Upload for a new Work Unit or an existing Work Unit associated with Uploads file.

Request

Your request to the Retrieve Upload Errors Service must provide a valid OAuth access token and a userId in the header. For instructions on how to obtain and use an OAuth Access Token programmatically, see Authentication. You can specify the following parameters in the request:

  • workUnitId (Required)
  • afterTimestamp
  • errorsOnly

You can also choose to display errors associated to upload attempts on or after the selected timestamp by using the parameter afterTimestamp. API requests with no timestamp default to display of all errors related to all upload attempts since 12:01 AM the current day. The API response will list up to 400 error messages for each product (i.e., Fares, Rules and Footnotes). If there are more than 400 errors per product, please manually log in Uploads File Management application in FareManager to view all errors an/or warnings. The display of 400 messages per product are prioritized with errors followed by warnings.

Request Header Parameters

See Authentication for instructions on header parameters needed for authentication.

Request URL Parameters

Request should contain Work Unit ID and any one of the following URL parameters

ParameterDescriptionTypeExample
workUnitIdUnique identifier assigned to the created work unitString"XXX-17MAR18-1234567"
afterTimestampTimestamp to retrieve upload error messages created on or after the specified time in Eastern Standard timeString"2019-07-24T00:01:00.000"
errorsOnlyFlag indicating retrieve only errors or errors and warnings. True is the default setting and returns only errors. Change the value to false to retrieve errors and warnings.String"true"

Response

Upon successful processing of a request, the Retrieve Upload Errors API will return a list of errors and/or warnings for the requested Work Unit ID and product type. The response to a successful Retrieve Upload Errors Service call will contain a JSON object including the parameters specified in the request.

Example Response Object with No Error Messages

Example Response Object with Errors and Warnings for Fares, Rules, and Footnotes Upload

Response Parameters

Rules Upload Errors and Warnings

ParameterDescriptionTypeExample
carrierCodeAs defined by ATPCO; generally an airlineString"XXX"
lineNumLine number in the rules upload file where the error/warning occurredString"4"
messageDescribes the rules upload error or warningString"Invalid number of records in the work unit of 00005"
ruleRule code associated with the tariffString"1680"
tariffCodeEntity that is defined by system, geographic scope, and distribution processString"IPRA"
timestampTimestamp of the rules uploadString"2019-12-18 14:51:07.104"

Footnotes Upload Errors and Warnings

ParameterDescriptionTypeExample
carrierCodeAs defined by ATPCO; generally an airlineString"XXX"
lineNumLine number in the footnotes upload file where the error/warning occurredString"4"
messageDescribes the footnotes upload error or warningString"Invalid number of records in the work unit of 00005"
tariffCodeEntity that is defined by system, geographic scope, and distribution processString"TAFP"
timestampTimestamp of the footnotes uploadString"2019-12-18 14:51:07.104"

Fares Upload Errors and Warnings

ParameterDescriptionTypeExample
carrierCodeAs defined by ATPCO; generally an airlineString"XXX"
fareKeyBatch and Transaction details
FareKey format for Transaction errors:
INTERNATIONAL - "F-BatchPrefixCd BatchNumber-LOC1-LOC2-FC-OW-FTN-RTG-CURR-EFFDT"
DOMESTIC - "V-BatchPrefixCd BatchNumber-LOC1-LOC2-FC-OW-FTN-RTG-CURR-EFFDT"
ADDON - "A-BatchPrefixCd BatchNumber-LOC1-LOC2-FC-OW-FTN-RTG-CURR-EFFDT-ZONE"
FareKey format for Batch level errors:
"B-BatchPrefixCd BatchNumber"
messageDescribes the fares batch data error or warning during fares uploadString"Invalid number of records in the work unit of 00005"
tariffCodeEntity that is defined by system, geographic scope, and distribution processString"TAFP"
timestampTimestamp of the fares uploadString"2019-12-18 14:51:07.104"

The Retrieve Upload Errors Service can give the following errors:

ErrorAffected ParameterDescription
Invalid format. Expected format is yyyy-MM-dd'T'HH:mm:ss.SSSafterTimeStampInvalid format
Work Unit ID has invalid length or formatworkUnitIdInvalid Work Unit ID
400 Bad RequesterrorsOnlyInvalid Flag