Backward compatibility

We will keep improving TilliT as a product and with that we will constantly update its API. However, we will do this while not introducing breaking changes. The following is a list of changes we may introduce in the future that we don't consider as breaking changes:

  • Adding new fields to objects

  • Adding new resources or endpoints

  • Adding new (optional) request parameters

  • Changing default page length for paginated resources

Please consider this when programming against the API and try to make sure these non-breaking changes don’t break your code.

If we introduce a breaking change, we will create new endpoints with a new version prefix in the URI.

Last updated