Design and management of OpenAPI contracts in a multi-country enterprise environment

The project was carried out within an enterprise environment with a central core system used across multiple countries. Communication between systems was implemented via a central integration layer built on OpenAPI contracts.

Individual countries had different requirements for data structures and API behavior, which complicated the design of a unified contract. Without a controlled change process, there was a risk of API inconsistency, regression errors, and unclear ownership of responsibilities.

• The need to maintain a unified central API contract
• Different regulatory and business requirements in individual countries
• Dependence on the existing core system and integration layer

Analyst responsible for one module of the OpenAPI specification, its analysis, change proposals, version management, and coordination with development teams and local stakeholders — drawing on direct involvement in a multi-country programme.

A controlled OpenAPI contract management process was introduced, with changes based on an analysis of individual countries' requirements. The central API design was gradually expanded to maintain compatibility, allow optional attributes for local needs, and remain sustainable in the long term.