ASC 2022 - API Specifications Conference

I would like to present you an innovative approach to design open APIs from business models.

This API Design First approach starts from the definition of the business use cases. Then the business models are designed, and finally, the open APIs specification are generated from the business models.

These models are designed at the entreprise level. A business concept is designed only once at the API level ... but also once at the whole enterprise level!

More than 95% of the time (workshops, modeling, design) is business oriented. Less than 5% is dedicated to technical design.
The approach is by the way, highly productive, consistent and error free.

To give you an order of magnitude, once business models are defined, a complex OAS (from 2000 to 3000 lines) is usually designed in less than 30 minutes with no error.

One of the main feature of the approach is that it allows to be focus on the business only.

This approach is currently implemented in the biggest french bank (BNP).

The approach is supported by a tool which convert business models to OAS then extends the specifications by adding http features.
This tool is called 'Swapi'.

The tool includes an http rules engine and check rules of an OAS but also among a set of OAS (for instance, a rule checks that a link in a response is consistent to the linked operation signature).

To be honest, I often think to myself when I design APIs: "How is it possible to design OAS in an other way?". This is the reason I would like to present this approach (and its relative tool to support it).

I can explain you the approach (powerpoint slides and/or show you a presentation in a real context)

This approach is also used to generate the 'Avro' schemas (and gRPC in a next future)