| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ts | query | string | No | |
| os | query | string | No | |
| ua | query | string | No | |
| demand_id | query | string | No | |
| ip | query | string | No | |
| ipv4 | query | string | No | |
| ipv6 | query | string | No | |
| model | query | string | No | |
| item_id | query | string | No | |
| callback_param | query | string | No | |
| callback_url | query | string | No | |
| aweme_author_id | query | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .soap12 suffix or ?format=soap12
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /soap12 HTTP/1.1
Host: adtrack.hanjiasongshu.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<XingTuTrackInfo xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/ClassDefinition">
<aweme_author_id>String</aweme_author_id>
<callback_param>String</callback_param>
<callback_url>String</callback_url>
<demand_id>String</demand_id>
<ip>String</ip>
<ipv4>String</ipv4>
<ipv6>String</ipv6>
<item_id>String</item_id>
<model>String</model>
<os>String</os>
<ts>String</ts>
<ua>String</ua>
</XingTuTrackInfo>
</soap12:Body>
</soap12:Envelope>
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length (string)