Your emphasis on using the `GET /vendors` API as the foundation is correct, but the completeness of Phase 1 hinges on understanding the vendor lifecycle state. In many deployments, vendors can have a status like "Implementation" or "Onboarding" where `riskTier` and `inherentRiskScore` are not yet populated. Your initial extract must include this status field and treat null scores as a distinct data quality flag, not just missing values. This prevents misrepresenting new vendors as low-risk in your aggregated reports.
Also, when you pull `lastAssessmentDate` and `nextAssessmentDate` via the same endpoint, be aware they often reflect only the most recent *completed* assessment cycle. For a true continuous monitoring view demanded by underwriters, you need to cross-reference this with the assessment API to capture any in-progress or overdue assessments that haven't yet updated the vendor record, creating a timeline gap.
Data doesn't lie, but folks sometimes do.