We take every precaution to ensure your content is safe from scrapers and bots.

As part of this process all requests to the Netcopy API and CDN must include a request authentication token. The benefits to this approach are:

• You can be sure that every successful request to your content was made by you.
• It is not possible to manipulate Netcopy API or CDN URLs to access other content.
• If you need to revoke your API key then all existing tokens generated with it will be automatically invalidated.
• It's fast, secure, and easy to implement!

Generating a request authentication token

Generating a request token is simple.

Concatenate your API key and request URL and MD5 the result, this will be your request token. You'll probably want to write a helper function to do this. For example:

    function generateToken( url )
    {
        var apiKey = "demo"
        var token = md5sum( apiKey + url )
        return token
    }

    var url =  "http://demo.content-api.netcopy.co.uk/search?term=test"
    var secureURL = url + "&token=" + generateToken( url )

    var search = http_decode_json( secureURL )
    print "Your search returned " + search.resultCount + " result(s)"

Please note! You must ensure that your token generation is done server-side. You cannot generate tokens in client-side Javascript as it would require exposing your API key.

Ways of passing your token

You can either pass your token as a URL parameter called token or via the X-Netcopy-Token HTTP header.