Sections in this category

Checking links

  • Updated


HTTP method Access rights URL Parameters Note
GET validate_links
  • link**
Returns the result of link check*.
  • * Returns the result in the JSON format.

  • ** We recommend to code the tested link in ULP in accordance to the standard RFC 2396.


Example of use

Example of a request with utility ``curl``:

curl -L -H 'Authorization: Bearer access_token' -X GET


Example of the response from the API server in the JSON format

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
"message": "Link successfully tested."


Description of API server response fields

Name Description
message Notification
Possible errors in the link:
  • Wrong domain name.

  • Wrong link.

  • Error in the address.

  • Code length must be 30 or 40 characters.

  • The code must contain letters a–f and digits 0–9.

  • Wrong ‘ulp’.

  • The SubID must be no more than 50 characters long.

  • Attention! The advertiser doesn’t pay any reward for selling the product corresponding to this link.

  • Attention! This product is non-affiliated.

  • This domain is not permitted for deeplink.

  • Inactive cooperation status.

  • The ad space is not active.

Was this article helpful?

0 out of 0 found this helpful