An API model represents the business operations and data models behind an API before they are expressed in an API definition. Designers derive it from user stories, job stories, the user journey, and domain modeling, using it to clarify the intended API before review. section 5.1
Use the model to:
- Make domain and design decisions explicit before proposing an API definition. section 5.1
- Give reviewers context for checking consistency and advising on API improvements. section 5.1
- Support an agreed API contract that server-side and client-side teams can build against. section 5.1
Figure 5.1 API reviews happen at the design stage of your APIOps workflow. API reviews start after the automated checks all pass. The API review is completed when all review comments have been resolved and the PR is merged.
Place API modeling before automated checks and API review in the APIOps design workflow. section 5.1
