Instant Tests

POST /instant/net/ping Ping

Runs an instant test in ThousandEyes, based on properties provided in the POST data. Instant tests can only be run programmatically against Enterprise agents (where "agentType": "Enterprise" from the /agents endpoint).

Instant tests are only accessible to users with Account Admin privileges.

Request

  • POST data must include the following fields:

    • agentID (integer), agentId from /agents endpoint
    • server (string), target for test
    • pingType (string), “ICMP” or “TCP”
    • port (integer), target for test, if pingType specified is TCP
  • The Content-Type header must be supplied, with a value of Application/json

Example

$curl -i https://api.thousandeyes.com/instant/net/ping.json \ -d '{ "agentId": 32, \ "server": "www.thousandeyes.com", \ "port": 80, \ "pingType": "TCP" \ }' \ -H "Content-Type: application/json" \ -u noreply@thousandeyes.com:g351mw5xqhvkmh1vq6zfm51c62wyzib2

Response

If a test is properly formatted, and the target agent is reachable, the request will be submitted, and a response will be returned based on the output of the test. Typically it will return an HTTP/200 OK response, along with the data (50 ping attempts) from the test. See the example below:

Note: the API sandbox account does not have access to run Instant Tests, so the following example is for documentation purposes only.

HTTP/1.1 200 OK Date: Thu, 07 Nov 2013 07:32:48 GMT Server: Apache/2.2.22 (Ubuntu) Transfer-Encoding: chunked Content-Type: application/json

Body

{ "net": { "ping": "78 bytes from 50.18.127.223: tcp_req=1 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=2 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=3 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=4 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=5 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=6 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=7 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=8 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=9 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=10 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=11 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=12 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=13 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=14 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=15 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=16 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=17 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=18 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=19 ttl=48 time=4 ms\n78 bytes from 50.18.127.223: tcp_req=20 ttl=48 time=4 ms\n78 bytes from 50.18.127.223: tcp_req=21 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=22 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=23 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=24 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=25 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=26 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=27 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=28 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=29 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=30 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=31 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=32 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=33 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=34 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=35 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=36 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=37 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=38 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=39 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=40 ttl=48 time=4 ms\n78 bytes from 50.18.127.223: tcp_req=41 ttl=48 time=4 ms\n78 bytes from 50.18.127.223: tcp_req=42 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=43 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=44 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=45 ttl=48 time=4 ms\n78 bytes from 50.18.127.223: tcp_req=46 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=47 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=48 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=49 ttl=48 time=5 ms\n78 bytes from 50.18.127.223: tcp_req=50 ttl=48 time=5 ms\n\n--- 50.18.127.223 ping statistics ---\n50 packets transmitted, 50 received, 0.0% packet loss\nrtt min/avg/max/mdev = 4.00/4.90/5.00/0.18 ms\n" } }

For error responses, see the response status codes documentation.

POST /instant/net/path-vis Path Visualization

Runs an instant test in ThousandEyes, based on properties provided in the POST data. Instant tests can only be run programmatically against Enterprise agents (where "agentType": "Enterprise" from the /agents endpoint).

Instant tests are only accessible to users with Account Admin privileges.

Request

  • POST data must include the following fields:

    • agentID (integer), agentId from /agents endpoint
    • server (string), target for test
    • pingType (string), “ICMP” or “TCP”
    • port (integer), target for test, if pingType specified is TCP
  • The Content-Type header must be supplied, with a value of Application/json

Example

$curl -i https://api.thousandeyes.com/instant/net/path-vis.json \ -d '{ "agentId": 32, \ "server": "www.thousandeyes.com", \ "pingType": "TCP", \ "port": 80 \ }' \ -H "Content-Type: application/json" \ -u noreply@thousandeyes.com:g351mw5xqhvkmh1vq6zfm51c62wyzib2

Response

If a test is properly formatted, and the target agent is reachable, the request will be submitted, and a response will be returned based on the output of the test. Typically it will return an HTTP/200 OK response, along with the data from 10 traces to the target server from the agent. See the example below:

Note: the API sandbox account does not have access to run Instant Tests, so the following example is for documentation purposes only.

HTTP/1.1 200 OK Date: Thu, 07 Nov 2013 07:32:48 GMT Server: Apache/2.2.22 (Ubuntu) Transfer-Encoding: chunked Content-Type: application/json

Body

{ "net": { "pathVis": [ { "countryId": "US", "server": "www.thousandeyes.com:80", "serverIp": "50.18.127.223", "routes": [ { "hops": [ { "hop": 1, "ipAddress": "10.0.200.1", "responseTime": 16 }, { "hop": 3, "ipAddress": "154.54.47.45", "prefix": "154.48.0.0/12", "rdns": "te0-2-0-1.mpd21.sfo01.atlas.cogentco.com", "network": "Cogent Communications (AS 174)", "responseTime": 6, "location": "United States" }, { "hop": 4, "ipAddress": "154.54.28.70", "prefix": "154.48.0.0/12", "rdns": "be2166.ccr21.sjc01.atlas.cogentco.com", "network": "Cogent Communications (AS 174)", "responseTime": 3, "location": "United States" }, { "hop": 5, "ipAddress": "154.54.6.106", "prefix": "154.48.0.0/12", "rdns": "be2000.ccr21.sjc03.atlas.cogentco.com", "network": "Cogent Communications (AS 174)", "responseTime": 3, "location": "United States" }, { "hop": 6, "ipAddress": "154.54.11.86", "prefix": "154.48.0.0/12", "rdns": "ntt.sjc03.atlas.cogentco.com", "network": "Cogent Communications (AS 174)", "responseTime": 3, "location": "United States" }, { "hop": 7, "ipAddress": "129.250.4.118", "prefix": "129.250.0.0/16", "rdns": "ae-4.r06.plalca01.us.bb.gin.ntt.net", "network": "NTT America, Inc. (AS 2914)", "responseTime": 3, "location": "Denver Area" }, { "hop": 9, "ipAddress": "205.251.229.46", "prefix": "205.251.228.0/22", "network": "Amazon.com, Inc. (AS 16509)", "responseTime": 4, "location": "Seattle Area" } ] }, { "hops": [...] }, { "hops": [...] }, { "hops": [...] }, { "hops": [...] }, { "hops": [...] }, { "hops": [...] }, { "hops": [...] }, { "hops": [...] }, { "hops": [...] } ], "locationName": "Office Canary (CentOS)", "agentId": 410 } ] } }

For error responses, see the response status codes documentation.

POST /instant/net/tcp-connect TCP Connect

Runs an instant test in ThousandEyes, based on properties provided in the POST data. Instant tests can only be run programmatically against Enterprise agents (where "agentType": "Enterprise" from the /agents endpoint).

Instant tests are only accessible to users with Account Admin privileges.

Request

  • POST data must include the following fields:

    • agentID (integer), agentId from /agents endpoint
    • server (string), target for test
    • port (integer), target for test
  • The Content-Type header must be supplied, with a value of Application/JSON

Example

$curl -i https://api.thousandeyes.com/instant/net/tcp-connect.json \ -d '{ "agentId": 32, \ "server": "www.thousandeyes.com", \ "port": 80, \ }' \ -H "Content-Type: application/json" \ -u noreply@thousandeyes.com:g351mw5xqhvkmh1vq6zfm51c62wyzib2

Response

If a test is properly formatted, and the target agent is reachable, the request will be submitted, and a response will be returned based on the output of the test. Typically it will return an HTTP/200 OK response, along with the time required to connect to the destination server. See the example below:

Note: the API sandbox account does not have access to run Instant Tests, so the following example is for documentation purposes only.

HTTP/1.1 200 OK Date: Thu, 07 Nov 2013 07:32:48 GMT Server: Apache/2.2.22 (Ubuntu) Transfer-Encoding: chunked Content-Type: application/json

Body

{ "net": { "tcpConnect": 7 } }

For error responses, see the response status codes documentation.

POST /instant/net/bandwidth Bandwidth

Runs an instant test in ThousandEyes, based on properties provided in the POST data. Instant tests can only be run programmatically against Enterprise agents (where "agentType": "Enterprise" from the /agents endpoint).

Instant tests are only accessible to users with Account Admin privileges.

Request

  • POST data must include the following fields:

    • agentID (integer), agentId from /agents endpoint
    • server (string), target for test
    • pingType (string), ICMP | TCP (defaults to TCP)
    • port (integer), used only when pingType is not set, or explicitly set to TCP. Accepts port values from 1 to 65535.
  • The Content-Type header must be supplied, with a value of Application/json

Example

$curl -i https://api.thousandeyes.com/instant/net/bandwidth.json \ -d '{ "agentId": 410, \ "server": "www.thousandeyes.com", \ "pingType": "TCP", \ "port": 80 \ }' \ -H "Content-Type: application/json" \ -u noreply@thousandeyes.com:g351mw5xqhvkmh1vq6zfm51c62wyzib2

Response

If a test is properly formatted, and the target agent is reachable, the request will be submitted, and a response will be returned based on the output of the test. Typically it will return an HTTP/200 OK response, along with the http-server data from the test. See the example below:

Note: the API sandbox account does not have access to run Instant Tests, so the following example is for documentation purposes only.

HTTP/1.1 200 OK Date: Thu, 07 Nov 2013 07:32:48 GMT Server: Apache/2.2.22 (Ubuntu) Transfer-Encoding: chunked Content-Type: application/json

Body

{ "net": { "metrics": [ { "countryId": "US", "agentName": "myagent.mycompany.com", "agentId": 993, "availableBandwidth": 393.1787, "capacity": 393.5404, "server": "www.thousandeyes.com:80" } ] } }

For error responses, see the response status codes documentation.

POST /instant/web/http-server HTTP Server

Runs an instant test in ThousandEyes, based on properties provided in the POST data. Instant tests can only be run programmatically against Enterprise agents (where "agentType": "Enterprise" from the /agents endpoint).

Instant tests are only accessible to users with Account Admin privileges.

Request

  • POST data must include the following fields:

    • agentID (integer), agentId from /agents endpoint
    • url (string), target for test
  • POST data can optionally include the following fields:

    • username (string), username for Basic or NTLM authentication.
    • password (string), password for Basic or NTLM authentication.
    • useNtlm (integer), 0 or 1, for when authentication is selected, 1 will enable NTLM. Default is 0.
    • postBody (string), include this data when using a POST request method
    • verifySslCertificate (integer), 0 or 1. Use 0 when a site is secured with a self-signed certificate. Default is 1.
    • sslVersionId (integer), [0|1|3] - set to the appropriate value. See the Test Metadata page for details.
    • headers (array of name/value pairs) (ie, User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0))
  • The Content-Type header must be supplied, with a value of Application/json

Example

$curl -i https://api.thousandeyes.com/instant/web/http-server.json \ -d '{ "agentId": 410, \ "url": "www.thousandeyes.com" \ }' \ -H "Content-Type: application/json" \ -u noreply@thousandeyes.com:g351mw5xqhvkmh1vq6zfm51c62wyzib2

Response

If a test is properly formatted, and the target agent is reachable, the request will be submitted, and a response will be returned based on the output of the test. Typically it will return an HTTP/200 OK response, along with the http-server data from the test. See the example below:

Note: the API sandbox account does not have access to run Instant Tests, so the following example is for documentation purposes only.

HTTP/1.1 200 OK Date: Thu, 07 Nov 2013 07:32:48 GMT Server: Apache/2.2.22 (Ubuntu) Transfer-Encoding: chunked Content-Type: application/json

Body

{ "web": { "httpServer": [ { "agentName": "Office Canary (CentOS)", "countryId": "US", "responseCode": 200, "numRedirects": 0, "errorType": "None", "dnsTime": 239, "connectTime": 6, "sslTime": 0, "waitTime": 438, "receiveTime": 5, "wireSize": 29931, "agentId": 410, "responseTime": 683, "fetchTime": 689 } ] } }

For error responses, see the response status codes documentation.

POST /instant/web/page-load Page Load

Runs an instant test in ThousandEyes, based on properties provided in the POST data. Instant tests can only be run programmatically against Enterprise agents (where "agentType": "Enterprise" from the /agents endpoint).

Instant tests are only accessible to users with Account Admin privileges.

Request

  • POST data must include the following fields:

    • agentID (integer), agentId from /agents endpoint
    • url (string), target for test
  • POST data can (optionally) include the following fields:

    • username (string), username for Basic or NTLM authentication.
    • password (string), password for Basic or NTLM authentication.
    • useNtlm (integer), 0 or 1, for when authentication is selected, 1 will enable NTLM. Default is 0.
  • The Content-Type header must be supplied, with a value of Application/json

Example

$curl -i https://api.thousandeyes.com/instant/web/page-load.json \ -d '{ "agentId": 410, \ "url": "www.thousandeyes.com" \ }' \ -H "Content-Type: application/json" \ -u noreply@thousandeyes.com:g351mw5xqhvkmh1vq6zfm51c62wyzib2

Response

If a test is properly formatted, and the target agent is reachable, the request will be submitted, and a response will be returned based on the output of the test. Typically it will return an HTTP/200 OK response, along with the page load data from the test. See the example below:

Note: the API sandbox account does not have access to run Instant Tests, so the following example is for documentation purposes only.

HTTP/1.1 200 OK Date: Thu, 07 Nov 2013 07:32:48 GMT Server: Apache/2.2.22 (Ubuntu) Transfer-Encoding: chunked Content-Type: application/json

Body

{ "web": { "pageLoad": [ { "agentName": "Office Canary (CentOS)", "countryId": "US", "dnsTime": 176, "connectTime": 102, "waitTime": 1199, "receiveTime": 817, "agentId": 410, "responseTime": 566, "fetchTime": 3544, "totalSize": 931782, "numObjects": 44, "numErrors": 0, "domLoadTime": 881, "pageLoadTime": 1058 } ] } }

For error responses, see the response status codes documentation.

POST /instant/web/transactions Transaction

Runs an instant test in ThousandEyes, based on properties provided in the POST data. Instant tests can only be run programmatically against Enterprise agents (where "agentType": "Enterprise" from the /agents endpoint).

Unlike other instant tests, transaction scripts must already exist in ThousandEyes to be run via instant test.

Instant tests are only accessible to users with Account Admin privileges.

Request

  • POST data must include the following fields:

    • agentId (integer), agentId from /agents endpoint
    • testId (integer), transaction test from /tests endpoint
  • The Content-Type header must be supplied, with a value of Application/JSON

Example

$curl -i https://api.thousandeyes.com/instant/web/transactions.json \ -d '{ "agentId": 410, \ "testId": 5069, \ }' \ -H "Content-Type: application/json" \ -u noreply@thousandeyes.com:g351mw5xqhvkmh1vq6zfm51c62wyzib2

Response

If a test is properly formatted, and the target agent is reachable, the request will be submitted, and a response will be returned based on the output of the test. Typically it will return an HTTP/200 OK response, along with the timing and error data from the transaction request. See the example below:

Note: the API sandbox account does not have access to run Instant Tests, so the following example is for documentation purposes only.

HTTP/1.1 200 OK Date: Thu, 07 Nov 2013 07:32:48 GMT Server: Apache/2.2.22 (Ubuntu) Transfer-Encoding: chunked Content-Type: application/json

Body

{ "web": { "transaction": [ { "agentName": "Office Canary (CentOS)", "countryId": "US", "stepsCompleted": 5, "totalSteps": 5, "componentErrors": 0, "agentId": 410, "transactionTime": 4828, "errorDetails": "" } ] } }

For error responses, see the response status codes documentation.

POST /instant/dns/trace DNS Trace

Runs an instant test in ThousandEyes, based on properties provided in the POST data. Instant tests can only be run programmatically against Enterprise Agents (where "agentType": "Enterprise" from the /agents endpoint).

Instant tests are only accessible to users with Account Admin privileges.

Request

  • POST data must include the following fields:

    • agentID (integer), agentId from /agents endpoint
    • domain (string), target for test
    • type (string), type of DNS record requested (eg, A, AAAA)
  • The Content-Type header must be supplied, with a value of Application/json

Example

$curl -i https://api.thousandeyes.com/instant/dns/trace.json \ -d '{ "agentId": 410, \ "domain": "www.thousandeyes.com", \ "type": "A" \ }' \ -H "Content-Type: application/json" \ -u noreply@thousandeyes.com:g351mw5xqhvkmh1vq6zfm51c62wyzib2

Response

If a test is properly formatted, and the target agent is reachable, the request will be submitted, and a response will be returned based on the output of the test. Typically it will return an HTTP/200 OK response, along with the DNS trace output from the test. See the example below:

Note: the API sandbox account does not have access to run Instant Tests, so the following example is for documentation purposes only.

HTTP/1.1 200 OK Date: Thu, 07 Nov 2013 07:32:48 GMT Server: Apache/2.2.22 (Ubuntu) Transfer-Encoding: chunked Content-Type: application/json

Body

{ "dns": { "trace": [ { "agentName": "Office Canary (CentOS)", "countryId": "US", "output": "com.\t172800\tIN\tNS\tj.gtld-servers.net.\ncom.\t172800\tIN\tNS\tc.gtld-servers.net.\ncom.\t172800\tIN\tNS\ta.gtld-servers.net.\ncom.\t172800\tIN\tNS\te.gtld-servers.net.\ncom.\t172800\tIN\tNS\tm.gtld-servers.net.\ncom.\t172800\tIN\tNS\tf.gtld-servers.net.\ncom.\t172800\tIN\tNS\tg.gtld-servers.net.\ncom.\t172800\tIN\tNS\tk.gtld-servers.net.\ncom.\t172800\tIN\tNS\ti.gtld-servers.net.\ncom.\t172800\tIN\tNS\tb.gtld-servers.net.\ncom.\t172800\tIN\tNS\tl.gtld-servers.net.\ncom.\t172800\tIN\tNS\td.gtld-servers.net.\ncom.\t172800\tIN\tNS\th.gtld-servers.net.\n;; Received 510 bytes from 192.33.4.12(c.root-servers.net.) in 32 ms\n\nthousandeyes.com.\t172800\tIN\tNS\ta1.verisigndns.com.\nthousandeyes.com.\t172800\tIN\tNS\ta2.verisigndns.com.\nthousandeyes.com.\t172800\tIN\tNS\ta3.verisigndns.com.\nthousandeyes.com.\t172800\tIN\tNS\tu1.verisigndns.com.\n;; Received 266 bytes from 192.48.79.30(j.gtld-servers.net.) in 138 ms\n\nwww.thousandeyes.com.\t120\tIN\tCNAME\tlb-www2-1897926422.us-west-1.elb.amazonaws.com.\n;; Received 95 bytes from 209.112.113.33(a1.verisigndns.com.) in 30 ms\n\namazonaws.com.\t172800\tIN\tNS\tu1.amazonaws.com.\namazonaws.com.\t172800\tIN\tNS\tu2.amazonaws.com.\namazonaws.com.\t172800\tIN\tNS\tr1.amazonaws.com.\namazonaws.com.\t172800\tIN\tNS\tr2.amazonaws.com.\n;; Received 196 bytes from 192.48.79.30(j.gtld-servers.net.) in 127 ms\n\nus-west-1.elb.amazonaws.com.\t300\tIN\tNS\tns-467.awsdns-58.com.\nus-west-1.elb.amazonaws.com.\t300\tIN\tNS\tns-1036.awsdns-01.org.\nus-west-1.elb.amazonaws.com.\t300\tIN\tNS\tns-1850.awsdns-39.co.uk.\nus-west-1.elb.amazonaws.com.\t300\tIN\tNS\tns-699.awsdns-23.net.\n;; Received 201 bytes from 156.154.64.10(u1.amazonaws.com.) in 40 ms\n\nlb-www2-1897926422.us-west-1.elb.amazonaws.com.\t60\tIN\tA\t184.169.129.227\nlb-www2-1897926422.us-west-1.elb.amazonaws.com.\t60\tIN\tA\t50.18.122.206\n;; Received 233 bytes from 205.251.193.211(ns-467.awsdns-58.com.) in 87 ms\n\n", "agentId": 410, "queries": 6, "finalQueryTime": 87, "mappings": "184.169.129.227\n50.18.122.206" } ] } }

For error responses, see the response status codes documentation.

POST /instant/dns/server DNS Server

Runs an instant test in ThousandEyes, based on properties provided in the POST data. Instant tests can only be run programmatically against Enterprise agents (where "agentType": "Enterprise" from the /agents endpoint).

Instant tests are only accessible to users with Account Admin privileges.

Request

  • POST data must include the following fields:

    • agentID (integer), agentId from /agents endpoint
    • server (string), target for test
    • domain (string) target domain name
    • type (string) target domain record type
    • queryClass (string), either “IN” (default), or “CH”. If omitted, type “IN” is assumed.
  • POST data can optionally include the following fields: * recursiveQueries (integer), 0 or 1 (defaults to 0). Set to 1 to set the Recursion Desired (rd) bit in the request

  • The Content-Type header must be supplied, with a value of application/json

Example

$curl -i https://api.thousandeyes.com/instant/dns/server.json \ -d '{ "agentId": 410, \ "domain": "thousandeyes.com", \ "type": "A", \ "server": "a1.verisigndns.com" \ }' \ -H "Content-Type: application/json" \ -u noreply@thousandeyes.com:g351mw5xqhvkmh1vq6zfm51c62wyzib2

Response

If a test is properly formatted, and the target agent is reachable, the request will be submitted, and a response will be returned based on the output of the test. Typically it will return an HTTP/200 OK response, along with the mapping and resolution time data from the test. See the example below:

Note: the API sandbox account does not have access to run Instant Tests, so the following example is for documentation purposes only.

HTTP/1.1 200 OK Date: Thu, 07 Nov 2013 07:32:48 GMT Server: Apache/2.2.22 (Ubuntu) Transfer-Encoding: chunked Content-Type: application/json

Body

{ "dns": { "server": [ { "agentName": "Office Canary (CentOS)", "countryId": "US", "agentId": 410, "server": "a1.verisigndns.com", "resolutionTime": 22, "mappings": "54.215.17.122" } ] } }

For error responses, see the response status codes documentation.