Skip to content

Roadmap

Jump to bottom
msacrea edited this page Jun 4, 2024 · 8 revisions

Please do not modify the name of this page ('Roadmap'). SFTI's GitHub infrastructure automations for API versioning releases rely on the structre of this page and its name. For more details see SFTI GitHub Actions.

2024

  • v1.0.0 - 4. Jun 24 : first major release

Release v1.0.0

This is the first major release of the SFTI pension API. It brings several new objects including a pension statement response optimized for QR code wrapping. Note that the simplified structure of the API and adherence to the new SFTI naming conventions come at the cost of several breaking changes.

  • Added pensions statement object pensionStatementBasic
  • Introducing new endpoint for compact JSON of pensionStatementBasic for QR code wrapping
  • Adding employer object to insuredPerson
  • Adding object pensionProvider
  • Extending interestRates object to also include rates for purchase calculations
  • Improving structure of riskBenefits regarding lump sum benefits
  • Merging policies.yaml, purchases.yaml and transactions.yaml into pension.yaml
  • Adding example values
  • Adopted new SFTI naming convention
  • Migrating from OpenAPI specification v3.0.1 to v3.1.0

2023

  • v0.8.0 - 21. Nov 23 : initial release

Release v0.8.0

We are excited to announce the first release of the SFTI Common API - Open Pension API, Version 0.8.0, marking a significant milestone in our journey towards enhancing digital pension data accessibility in Switzerland. This release builds upon the foundational work of SFTI’s OpenPK working group and the initial API definition by the SFTI member company Acrea. With this release, the initial API definition is fully transitioned to SFTI Common API. As we launch this new chapter on our dedicated GitHub repository, please note that the original OpenPK repository will be decommissioned. The new version does not introduce new features, it incorporates minor adjustments adhering to the SFTI Common API formatting and coding standards (i.e. only minor and no breaking changes). We look forward to your valuable feedback and collaboration in shaping the future of Open Pension in Switzerland.

  • add specifications
  • add lint workflow
  • align specifications to SFTI style guides
  • adjust api contact infos
  • Apache-2.0 license
  • add release workflow

SFTI | ca-pension

Wiki

API specific Information

Version Management

Common Implementation Guidelines

Clone this wiki locally