Skip to main content

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 change the URL to api.apaleo.com, and 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.

Comments

Popular posts from this blog

Getting Started with apaleo APIs

Have a look You can find all of apaleo's API on api.apaleo.io. We use Swagger to describe it, and to generate our documentation.

Sign up The first step is to sign up for an account. After you finish signup you will be able to login to our apaleo app and start configuring your properties. Also you can use the same credentials to access our API using Swagger. Get access for app We're still new and want to get in touch with you before we grant you access. Contact us at api@apaleo.com, to get your very own client credentials that lets you play with the API in our sandbox.
Use it apaleo APIs are protected using OAuth2 - the de-facto standard for API security. Here's a short guide to get you started:

Step 1: To get access to our APIs, you need to use your client id and secret to obtain an access token. Don't have one? Contact us at api@apaleo.com.

Combine your client id and secret into a string, separated by colon yourClientId:YourClientSecret and encode with Base64. This wi…

Connect your app with OAuth 2.0

What is this all about? When you connect your app to apaleo, it can read or modify data, or even trigger entire business flows of a hotel. But before gaining access to any of the resources in the REST API, it must get permission from the hotel. This guide will walk you through the authorization process (described in greater detail by the OAuth 2.0 specification). Note: apaleo's OAuth 2.0 implementation supports the standard authorization code grant type. You should implement the application flow described below to obtain an authorization code and then exchange it for a token. (The implicit grant type is not supported.) Terminology Before learning more about the details of the authorization process, make sure that you are familiar with some of the key terms that are used in this guide: Client: Any application that would like access to a hotel's data. A user (usually the hotel's owner or admin) must grant permission before the client can access any data.API: apaleo REST API. T…

Channel Integration Guide

With the channel integration you can subscribe for availability, rates and inventory (ARI), create new bookings and modify existing bookings. 
The BasicsGet your sandbox account and check out this guide to learn how you can connect to the apaleo APIs.
API Client All apaleo APIs are described as swagger documents. That lets you generate API clients directly from the swagger.json files. There is a large community, providing client generators for almost every language. For example, swagger code generator is a good project, which allows generation of API clients for Java, PHP, C#, NodeJS and more. This gets you up to speed very fast and as a bonus you can access API documentation within the auto-generated methods and models.
Sandboxapaleo.io is our – and your – playground to do first steps with the API, up to your final integration. Use it to interactively explore the API or to learn the apaleo concepts by navigating the user interface.

These are the links you need to know