We’re going live!
And we need to talk.
Apart from us being super happy and excited, this also means some changes for you, and us, and the way we work together.
If you already are working with apaleo APIs, here are the biggest changes for you:
- the APIs will be available under api.apaleo.com
- we’ll start versioning the API. That gives us the possibility to roll out new features and API changes, without breaking your stuff.
- we improved the security concept, as we’ll now deal with real user data
What does this mean for you now?
All you’ll need to do, is include the version in the path, like so: api.apaleo.com/booking/v1/(the rest stays)
When you request an access token, specify either the scopes you want (find them in the API documentation), or just leave it blank – you will then get a token allowing to access all the APIs we opened up for you.
In addition, we started creating new clients for every customer, to ensure strict data separation. A new set of credentials will be sent to you soon. On your side, you’ll need to use the right client when requesting access. For example, if you want to access the data of a customer ‘Amazing Place’, you’ll need to get a token using the ‘Amazing Place’ client credentials.
What does this mean for you in the future?
We’ll obviously continue rolling out new features and changing the API, but now that we have versioning in place, you can be sure that things don’t suddenly break as long as you stay on the same version (and everyone: YEAH, no more breaking changes!)
However, keeping the previous versions around for too long will impact our speed to deliver new stuff (now everyone: OH NO!), which means they’ll disappear after a while. More specifically, three months after we inform you about the change, and give you a guide and the possibility to migrate to the new stuff. If you cannot make it in time, ping us and we can see if we can extend that. We know that you also have other projects, and deadlines, and might not always be able to make the move within this timeframe.
For the impatient and curious, we will also make a sneak-preview version of the API available, coming with no guarantees, but the hottest new features and changes, some of them experimental. You’ll find those under the version name ‘nsfw’, as they are ‘not safe for work’: api.apaleo.com/booking/v0-nsfw/…
We’ll keep you up to date about upcoming changes and new features, right here.
Thanks to all our partners and friends, for your trust and braveness to develop on apaleo, while it was still in a beta phase.
You are awesome.