Get the traffic volume in megabytes from the origins of all your domains by acceleration region. The region can be 'cn', 'nc', 'euna', or 'apac' representing Mainland China, near China, Europe/North America, and Asia Pacific, respectively. You may specify more than one area by separating them with semicolons. Request parameters allow you to specify a time period, an interval type, and timezone for the output. An optional parameter lets you get HTTPS traffic only or HTTP traffic only.
Header |
Description |
Required |
Authorization |
Authorization string for the request |
Yes |
Host |
URI for the QUANTIL SDK (i.e., api.quantil.com) |
Yes |
Date |
The date and time of the request. |
Yes |
Accept |
Indicates the accepted format (i.e., application/xml) |
Yes |
Parameter |
Description |
Required |
datefrom |
RFC3339 formatted date indicating the starting date. Example: 2013-01-01T22:30:00+08:00 |
Yes |
dateto |
RFC3339 formatted date indicating the ending date. Example: 2013-01-01T22:30:00+08:00 |
Yes |
type |
Indicates the granularity of time. Can be fiveminutes, hourly, or daily. |
Yes |
timezone |
Indicates the timezone for the report data. It must be relative to GMT and specified in the format GMT+n where -12<= n <= 12. For example, timezone=GMT-7 and timezone=GMT+8. If the parameter is unspecified, results will be in the GMT timezone. |
No |
https |
If true, return traffic for domains using SSL. If false, return traffic for domains not using SSL. If not specified, return all traffic (SSL and non-SSL). |
No |
This request does not include an XML document in the request body.
GET /api/report/flow/origin HTTP/1.1
Authorization: <authorization string>
Host: api.quantil.com
Date: <date>
Accept: application/xml
Here is the structure of a request using the curl utility.
curl -i --url https://api.quantil.com/api/report/flow/origin/{region}?datefrom = {date from} & dateto = {date to} & type = {fiveminutes or hourly or daily} & timezone = {timezone}
-X GET
-u {user}: {password}
-H 'Date: Fri, 26 Oct 2012 06:33:26 GMT'
-H 'Accept: application/xml'
curl -i --url 'https://api.quantil.com/api/report/flow/origin/euna?datefrom=2014-08-01T00:00:00%2B09:00&dateto=2014-08-02T23:59:59%2B09:00&type=fiveminutes' -u test:Yzmnz8o32ZwxwTjHjTWsrIVV96Y= -H 'Date: Thu, 07 Aug 2014 13:46:34 PDT'
HTTP/1.1 200 OK
Date: <date>
Content-Type: application/xml; charset = utf-8
x-cnc-request-id: {id string auto generated by the QUANTIL server}
Element |
Description |
flow-report |
container for traffic information. It will contain one <flow-summary> child element and zero or more <flow-data> child elements indicating volume at different times. |
flow-summary |
indicates total volume in megabytes |
flow-data |
this container object contains a <timestamp> element and a <flow> element describing the traffic volume (in megabytes) at a particular time. |
timestamp |
indicates the date and time |
flow |
indicates traffic volume in megabytes |
The following example shows data at five minute intervals.
HTTP/1.1 200 OK
Date: Thu, 07 Aug 2014 20:51:27 GMT
Accept-Ranges: bytes
Server: WS-web-server
x-cnc-request-id: 1129283
ContentType: application/xml;charset=UTF-8
Content-Type: application/xml;charset=UTF-8
Content-Length: 1293
<flow-report>
<flow-summary>2508724.0</flow-summary>
<flow-data>
<timestamp>2014-07-31 23:00:00</timestamp>
<flow>163821.0</flow>
</flow-data>
<flow-data>
<timestamp>2014-07-31 23:05:00</timestamp>
<flow>197421.0</flow>
</flow-data>
<flow-data>
<timestamp>2014-07-31 23:10:00</timestamp>
<flow>255564.0</flow>
</flow-data>
<flow-data>
<timestamp>2014-07-31 23:15:00</timestamp>
<flow>216326.0</flow>
</flow-data>
<flow-data>
<timestamp>2014-07-31 23:20:00</timestamp>
<flow>260566.0</flow>
</flow-data>
<flow-data>
<timestamp>2014-07-31 23:25:00</timestamp>
<flow>329685.0</flow>
</flow-data>
<flow-data>
<timestamp>2014-07-31 23:30:00</timestamp>
<flow>144774.0</flow>
</flow-data>
<flow-data>
<timestamp>2014-07-31 23:35:00</timestamp>
<flow>125037.0</flow>
</flow-data>
<flow-data>
<timestamp>2014-07-31 23:40:00</timestamp>
<flow>259759.0</flow>
</flow-data>
<flow-data>
<timestamp>2014-07-31 23:45:00</timestamp>
<flow>183625.0</flow>
</flow-data>
<flow-data>
<timestamp>2014-07-31 23:50:00</timestamp>
<flow>226576.0</flow>
</flow-data>
<flow-data>
<timestamp>2014-07-31 23:55:00</timestamp>
<flow>145570.0</flow>
</flow-data>
</flow-report>
Error |
Description |
HTTP status code |
InvalidDatePeriod |
The date specified is invalid. |
400 |
InvalidReportType |
The report type specified is invalid. |
400 |
InvalidServiceArea |
The specified region is invalid. |
400 |