> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/api-wen-dang/api-reference/post-booking-apis/regenerate-order-1.md).

# 确认行李损失

{% hint style="info" %}
💬 **需要帮助？** 如果遇到问题，请在帮助中心咨询 Eva，快速获取诊断建议。

<a href="https://www.atriptech.com/" class="button primary" data-icon="comments">咨询 Eva</a>
{% endhint %}

用于处理 OTA 随单行李加购中航司报价高于 OTA 售价的情况。

收到 `3011` 后，传入 `orderNo` 确认亏出，系统继续完成行李加购和出票。

请在 30 分钟内完成确认。超时未确认的订单会自动取消。

完整的接入规则、异常处理和结算方式，请参阅 [OTA 随单行李加购](/api-wen-dang/product-guides/extensions-and-integrations/special-integrations/zhong-guo-ota-sui-dan-xing-li-jia-gou.md)。

## Confirm Baggage Price Change

> \*\*Purpose:\*\*\
> Confirm acceptance of the airline baggage price increase for an OTA order that is waiting for baggage price change confirmation.\
> \
> \*\*Prerequisite:\*\*\
> The order must have received baggage price change error \`3011\` and must still be within the configured confirmation period.\
> \
> \*\*Endpoint:\*\*\
> <https://sandbox.atriptech.com/confirmBaggageLoss.do\\>
> \
> \> The client identity is obtained from the authentication headers. Do not send \`cid\`, sub-order number, or a separate confirmation flag in the request body.

```json
{"openapi":"3.0.1","info":{"title":"Default module","version":"1.0.0"},"security":[],"paths":{"/confirmBaggageLoss.do":{"post":{"summary":"Confirm Baggage Price Change","deprecated":false,"description":"**Purpose:**\nConfirm acceptance of the airline baggage price increase for an OTA order that is waiting for baggage price change confirmation.\n\n**Prerequisite:**\nThe order must have received baggage price change error `3011` and must still be within the configured confirmation period.\n\n**Endpoint:**\nhttps://sandbox.atriptech.com/confirmBaggageLoss.do\n\n> The client identity is obtained from the authentication headers. Do not send `cid`, sub-order number, or a separate confirmation flag in the request body.","tags":[],"parameters":[{"name":"Accept","in":"header","description":"","required":true,"schema":{"type":"string"}},{"name":"Content-Type","in":"header","description":"","required":true,"schema":{"type":"string"}},{"name":"Accept-Encoding","in":"header","description":"","required":true,"schema":{"type":"string"}},{"name":"x-atlas-client-id","in":"header","description":"","required":true,"schema":{"type":"string"}},{"name":"x-atlas-client-secret","in":"header","description":"","required":true,"schema":{"type":"string"}}],"requestBody":{"content":{"application/json":{"schema":{"type":"object","properties":{"orderNo":{"type":"string","description":"Atlas main order number that is waiting for baggage price change confirmation."}},"required":["orderNo"]}}},"required":true},"responses":{"200":{"description":"","content":{"application/json":{"schema":{"type":"object","required":["status","msg"],"properties":{"status":{"$ref":"#/components/schemas/BaggageLossConfirmStatus"},"msg":{"$ref":"#/components/schemas/ResponseMessage"},"requestId":{"type":"string","description":"Atlas request identifier.","nullable":true},"clientRequestId":{"type":"string","description":"Client request identifier, when supplied by the caller.","nullable":true}}}}},"headers":{}}}}}},"components":{"schemas":{"BaggageLossConfirmStatus":{"type":"integer","description":"- `0`: Confirmation accepted.\n- `336`: No pending baggage price change confirmation exists for this order.\n- `337`: Confirmation period has expired.\n- `800`: Order does not exist.\n- `902`: The order does not belong to the authenticated client.\n- `9999`: Internal error.","enum":[0,336,337,800,902,9999]},"ResponseMessage":{"type":"string","description":"It serves as an additional description of the response result. Especially when the interface reports an error (`status` !=`0`), it is usually a human-readable error message. Note: Do not use this field in any programming scenarios. For example, do not judge whether the interface responds successfully based on this field. Instead, you should only determine it by checking whether the status is equal to`0`at any time."}}}}
```
