At this point in the API design process, digital capabilities have been identified using job stories. Activities required to produce the outcomes have been captured based upon insights from an EventStorming session. By starting with a focus on outcomes and activities, teams remain aligned with the needs of customers and business goals.
The next step in the API design process is to identify candidate APIs. These candidate APIs will reflect one or more boundaries that are identified using an EventStorming canvas or list of activities produced from the previous step. As the boundaries are identified, an API profile begins to emerge.
The API profiles provide more detailed clarity about each API and will be used to inform the eventual API design. It reflects the API resources that will need to be designed, along with the operations that will be offered. This definition step is essential in designing an API that is focused on delivering the desired outcomes of customers, partners, and the workforce.