Go directly to contents.
Best practices for developers
API design in public administration
  1. Guide's start page
  2. Before procurement
  3. During the development process
  4. When a program or application has been completed
    1. Publish the data model and source code openly
    2. Support software developers
    3. Create a high-quality deployment process
    4. Publish the life cycle and create versioning
    5. Support experiments and use
    6. Plan retirement
      1. Minimize disruption from retirement
      2. Communicate about retirement in time
  5. Glossary

Plan retirement

Minimize disruption from retirement

All software, hardware and regulation have a life cycle. Practical experience has shown that transferring integrations implemented with older technologies to a cloud platform reduces their number by about 30% on average.

When an API is retired, it is important to manage the dependencies associated with it to minimise any disruption caused.

Updated: 5/5/2026

Communicate about retirement in time

It is important to plan for the retirement of an API or its older version. This process must be observed to manage the partner network's and ecosystem's dependencies.

Users should be informed of the fact that the API is reaching the end of its life cycle in good time, at least several months in advance. The users must be given sufficient time to either update the API to a newer version or switch to replacement solutions.

Updated: 5/5/2026

Are you satisfied with the content on this page?

Glossary