Starting today, we’re beginning to roll out a change to the way the PlanningAlerts API works. We’re introducing API keys for all users of the API from low-volume non-commercial users to high-volume commercial users. We are making this change so that we can better measure and understand the way people are using the API as well as give us the ability to contact all API users in case of any issues (or changes we make) that might affect them.
We’re phasing in the introduction of API keys. Right now they are optional, though as a new user of the API you will be guided into using them.
On 1st of June 2015 the use of API keys will become mandatory
3 months from now on 1st of June 2015 the use of API keys will become mandatory.
This means if you are a user of the API today, you will need to move over to using API keys before 1st of June 2015. If you don’t do it by then the API will stop working for you on that date.
We’ve made it very easy for you
Thankfully, we’ve made it very easy for you to get an API key.
- Simply register for an account on PlanningAlerts
- Then visit the normal API documentation page to see your API key
- Update your API calls adding
&key=[your key]
We recommend you don’t use the PlanningAlerts api via client-side javascript
If you use the API in client-side javascript you will obviously be sharing your api key with the world which is a very bad thing. It is your responsibility to keep the api key safe and secure. If we discover any abuse of a key (e.g. someone else is using your key) we will cancel the key and you will have to get another one.
As a result we recommend you don’t use the PlanningAlerts api via client-side javascript.
Either
- Switch to getting the planningalerts data server-side where you won’t expose the api key
- Or proxy the client-side requests through your own server where you add the api key
If you have any questions on how to do this, of course don’t hesitate to get in touch with us.
Facebook
Instagram
Twitter