Sabre Bargin Finder Max REST API 请求无效问题求助
Sabre Bargain Finder Max API 请求错误排查求助
当前调用详情
- 请求地址:
https://api-crt.cert.havail.sabre.com//v4/offers/shop - 请求头:包含
Authorization: Bearer {token} - 请求体:
{ "OTA_AirLowFareSearchRQ": { "POS": { "Source": [ { "PseudoCityCode": "PCC_CODE", "RequestorID": { "ID": "1", "Type": "1" } } ] }, "OriginDestinationInformation": [ { "DepartureDateTime": "2024-10-01T00:00:00", "OriginLocation": { "LocationCode": "KTM" }, "DestinationLocation": { "LocationCode": "DXB" }, "RPH": "1" }, { "DepartureDateTime": "2024-10-28T00:00:00", "OriginLocation": { "LocationCode": "DXB" }, "DestinationLocation": { "LocationCode": "KTM" }, "RPH": "2" } ], "TravelerInfoSummary": { "AirTravelerAvail": [ { "PassengerTypeQuantity": [ { "Code": "ADT", "Quantity": 1, "Changeable": true } ] } ] }, "Version": "4" } }
v4版本请求错误响应
{ "groupedItineraryResponse": { "version": "6.3.0", "messages": [ { "severity": "Info", "type": "SERVER", "code": "GCA14-ISELL-TN-00-2024-10-00-9LFK", "text": "27131" }, { "severity": "Info", "type": "WORKERTHREAD", "code": "TRANSACTIONID", "text": "7364989799406789611" }, { "severity": "Error", "type": "SERVER", "code": "INVALID", "text": "Bad request", "value": "Invalid request" }, { "severity": "Error", "type": "MAIN", "code": "INVALIDREQ", "text": "Incorrect GIR response schema version used" }, { "severity": "Error", "type": "ERR", "code": "ERR", "text": "Error during Processing" } ], "statistics": { "itineraryCount": 0 } } }
尝试v2版本后的错误响应
{ "status": "NotProcessed", "type": "Application", "errorCode": "ERR.2SG.CLIENT.INVALID_REQUEST", "timeStamp": "2024-09-26T10:10:47.291Z", "message": "Client invalid path, not found in rest table" }
排查建议
- 修正URL格式:原地址中
//v4存在多余斜杠,改为/v4后重试 - 核对版本匹配性:v4 API返回的错误提示"Incorrect GIR response schema version used",需确认请求体中
OTA_AirLowFareSearchRQ.Version字段值是否与v4 API要求的schema版本一致 - 确认v2 API路径:直接替换版本号为v2出现路径不存在错误,需查找Sabre官方文档中Bargain Finder Max v2的正确端点路径
- 验证PCC有效性:确保
PseudoCityCode填入的是有效的Sabre伪城市代码,无效代码会导致请求验证失败 - 检查请求头完整性:确认是否添加了
Content-Type: application/json这类必填请求头,缺失可能引发格式错误
内容的提问来源于stack exchange,提问作者Sibindra Timalsina
相关产品推荐
相关产品推荐

