As of July 2019 we are no longer accepting calls to our API version 1 from new origins.
If you have built integrations or other features based on our API version 1 and have made calls to it within the last few months, then we are aware and your API access will continue to work.
If you find that this is not the case, please get in touch with us via firstname.lastname@example.org
Why has it been deprecated?
Version 1 of our API, while still fully secure and working, was no longer state-of-the-art in terms of its structure but also its authentication method. Further certain data points that you would expect our API to include were not available as version 1 lagged behind our range of new product additions over the last few years.
Is that it, no more API?
No, on the contrary. As you can tell by reading between the lines above, we have version 2 of our API almost ready to go and will launch it in stages over the coming months.
...and it is time to get excited about it as it will include:
- better documentation: written with tech audience in mind. It means you or your team does not have to be an expert in eHQ anymore to understand and consume our API
- more and better defined query params: more efficient ways to call exactly the data you need
- GET and POST requests: the ability to not only read data from your eHQ, but write data too
- state-of-the-art authentication methods: token based authentication and eventually OAuth2.0
- multiple tiers of access
When can I have access?
BETA access to our API version 2 is currently only provided on a case by case basis. If you do want to explore it get in touch with us and we can talk you through the new API and its different levels of access.