Skip to content

Feature maturity

Our online services and APIs are evolving rapidly. In order to make improvements quickly, we sometimes have to break an existing API. To set the correct expectations for developers, we have introduced 3 levels of feature maturity. Please consider these levels when determining the expected maintainance effort for your integration.

Alpha

  • Availability: limited group of customers via feature flagging and/or white listing.
  • Goal: Early testing to gather feedback before maturing the feature.
  • Documentation: generated API specs are available, but no documentation is available.
  • Stability: breaking changes may (and likely will) be introduced.

Beta

  • Availability: available to all customers and API consumers (depending on subscription level).
  • Goal: receive feedback on nearly completed functionality.
  • Documentation: generated API specs are available, draft documentation is available.
  • Stability: breaking changes may be introduced, but with more caution.

Generally Available (GA)

  • Availability: available to all customers and API consumers (depending on subscription level).
  • Goal: full functionality to be used in production environments.
  • Documentation, generated API specs are avialable, documentation is available.
  • Stability: breaking changes will not be introduced, unless a critical bug fix or security fix has to be addressed.

Warning

Currently our API specs do not indicate wich level of maturity applies to a certain endpoint. If you are unsure, please reach out to us to confirm that the endpoint you intend to use is stable enough for your purposes. A future update to the API specs will address this issue.