API Deprecation

We have recently recieved notice that the existing quickfile API will stop working as of June 2027. We have a large number of integrations that use the existing API and migrating them to the new API represents a significant effort.

Is there any way that the current API can be left operational (it would be okay if this is without future development or maintainence), and the new API given a new base url instead e.g. https://api.quickfile.co.uk/v2 ?

Hi @Adam_Johnston

Unfortunately it’s not going to be possible for us to keep the older API running past the June 2027 timeline.

We do appreciate it’s going to be a bit of work, which is why we’ve given 9 months notice on this.

The newer API is more flexible, secure and easier to manage (with improved rate limiting, too). And as it has Swagger docs, it can generate an SDK to help make life easier with development.

Is there any particular part that is causing a concern for the upgrade? I can generate an SDK for you if that would be helpful?