Factorial's API to the next level

In these last quarter, we have driven the Factorial's public API to first class. We have set the foundations for a fully stable and versioned public API. This means we have set the following changes:

Stabilizing version v2

V2 version has been in the oven for several months. Last July, we started to publish in v2 everything missing from v1. All the functionality in v1 must be now available in v2. If this is not the case, please contact us and let us know

We finally released v2 version at the beginning of September, deprecating v1 version

Versioned v2: 2024-10-01 and next

But we didn't stop here. Factorial's product teams move fast. They are constantly improving to deliver value to our clients. And the public API improves with them. Many of the new features are exposed to the public API, so our clients and developer partners can use them and bring more value to our users.

On the other hand, we know that public API consumers have their own pace. Keeping up to date with Factorial's API changes is probably not the first thing on their ToDO list.

This is why we are introducing API versioning in our v2 public API version. Every quarter, we are evolving our v2 version to new releases, without losing backwards compatibility within a year. This way, we give our API consumers enough time to adapt to new changes, while our product teams evolve fast.

Upgrading to newer versions should be must easy, just changing the paths most of the time. We will be publishing a detailed changelog, like 2024-10-01 Release Notes so clients and partners are able to easily upgrade.

Deprecating v1

Our v1 version has served us well for years, but it has several flaws and we need to move on. V1 version will keep working until April 1st, 2025. Afterward, it will be removed. Working webhooks will be automatically migrated to v2.