Partner Create/Reply Event Interface

Point-to-point support: Optional

Update Date: 2026-07-01 Suppliers providing services in China Mainland mandatory, suppliers providing services in Hong Kong, Macau, Taiwan and overseas are recommended. Online test(Sandbox)

Summary

This interface is used to send new customer service events to Ctrip or reply to customer service events sent by Ctrip, and also supports penalty appeals
Customer service events only support one request and one reply, not multi-round communication. That is, Ctrip initiates event → partner replies to event, partner initiates event → Ctrip replies to event, and the current event is closed after reply
Penalty events support multi-round communication, such as: Ctrip initiates penalty → partner initiates appeal → Ctrip replies to appeal → partner continues to appeal until reaching the maximum number → penalty execution result notification

API Address

Address Format: {Domain}/JNT-{vendorID}/event/push/2.0/{ctripPurchaseOrderID}/{timeStamp}/{sign}

Request Payload

ConfirmOrderRequest

Parameter	Type	Required	Description	Example
ctripPurchaseOrderId	Long	Y	Ctrip Order ID, returned from create order interface
vendorOrderId	String	Y	Vendor Order ID
serviceProviderId	Long	Y	Service Provider ID
eventSource	Integer	Y	Event Source: 1-Customer Service Event, 2-Penalty Event
pushType	Integer	Y	Push Type: 1-Create, 2-Reply, Note: Penalty events only support reply (i.e., appeal)
vendorEventId	String	Y	Unique ID provided by vendor after customer service or penalty event transmission (for troubleshooting only)
ctripEventId	Long	N	Used for event reply scenario, fill in the latest event id for customer service events, appeal id for penalty events, indicating which event or penalty is being replied to
eventTypeId	Integer	N	Event Type ID, required when eventSource = 1	Event Type List
content	String	Y	Reply content of event or supplementary content of penalty appeal, HTML syntax
singleCallBack	Bool	N	Receipt result, only has value when eventSource=1&&pushType=2, usually used for verification events, true=confirmed/agree, false=not confirmed/disagree
operator	String	Y	Handler ID, used for online troubleshooting
punishId	long	N	Penalty ID, passed when appealing (i.e., eventSource==2&&pushType==2)
appealId	long	N	Appeal ID, not empty when appealing (i.e., eventSource==2&&pushType==2)
appealOperate	String	N	Appeal Operation: "CONFIRM"-Accept penalty, "APPEAL"-Initiate appeal, not empty when replying to penalty event
appealCode	String	N	Appeal code, fill in the code from AppealLabelDTO in penalty interface, not empty when appealing
appealReason	String	N	Appeal reason, fill in the label name from AppealLabelDTO in penalty interface, not empty when appealing
enclosure	List<EnclosureDTO>	N	Attachment

EnclosureDTO

Parameter	Type	Required	Description	Example
fileType	String	Y	File type (lowercase)	File Type List
fileName	String	Y	File name
fileUrl	string	N	File address, required when appealing penalty event, fill in the file link generated after uploading to Ctrip server (see Upload Attachment API)

Response Payload

ConfirmOrderResponse

Parameter	Type	Required	Description	Example	Note
msgCode	String	Y	Response Code	OK	Response Code
message	String	N	Response Detail	Success	Response Code
eventId	String	Y	Customer service event scenario returns Ctrip's event ID, penalty scenario returns penalty order ID

Request Example

{
    "content": "After verification through order full call recording and trip-related information, your complaint is established [Refund 30.6 yuan], we sincerely apologize for the bad experience. The driver issue has been handled according to platform rules, and the platform will continue to strengthen supervision. Thank you for your understanding and support.",
    "ctripEventId": "231277355",
    "ctripPurchaseOrderId": "145564098833989758",
    "eventSource": 1,
    "eventTypeId": "",
    "operator": "Sunshine Customer Service",
    "pushType": 2,
    "serviceProviderId": 1000009,
    "vendorEventId": "23C21118312",
    "vendorOrderId": "23C4PPEE1BWS0BT"
}

Response Example

{
    "msgCode": "OK",
    "massage": "Success"
}

Error Example

{
    "msgCode": "ERROR_URL_PARAM",
    "massage": "Invalid URL format"
}

Partner Create/Reply Event