Content API is secured using API key based authentication, this key not only determines if you're permitted to access the API but also what content you're entitled to consume.
When developing against Content API it's essential you identify yourself with your API key for every single request. You can provide the key via two mechanisms, a header or a query parameter.
Passing the API key via the "apikey" header is the recommended approach and can be achieved as follows:
curl \ -H "apikey: <API KEY>" \ https://content.api.pressassociation.io/v1
For those situations when passing a header isn't possible (e.g. a legacy web application using JSON-P or perhaps CMS that supports Atom/RSS but doesn't allow a header to be provided you can also use the "apikey" query parameter:
curl https://content.api.pressassociation.io/v1?apikey=<API KEY>
Updated over 2 years ago