Over the coming months, we will move to a new version of the ESCO API. The change is part of our ongoing work to make ESCO more secure, easier to use and ready for future developments. 

Why are we making this change? Technology and security standards are constantly evolving, and we want to ensure that the ESCO API keeps pace. The new version will provide a safer and more reliable service, while giving us a stronger foundation for future improvements. We have also taken on board feedback from organisations and developers who use ESCO, which has helped us identify areas where the API can be made easier to work with.

What is changing? We are upgrading the ESCO API to a new, Open API-based version. The local ESCO API will also be updated as part of this transition.  As part of the upgrade, users will need to request and obtain an API key to access the API. This new process is designed to enhance security, improve service reliability and provide a better overall user experience. Additional guidance and step-by-step instructions on how to request and manage an API key will be made available before the change comes into effect.

Looking for an alternative? As part of this transition, the local API will also move to the new OpenAPI-based version described above.