LeanIX v4 Official Docs Lag Behind API Reality
1 What happened
During the unified LeanIX catalog schema work (MET-0002), we discovered that the official LeanIX v4 documentation was incomplete — the Pathfinder API exposed fields and relationships not described in the published metamodel PDF. The auto-research loop iterated 10 rounds to reconcile official docs vs. actual API responses, revealing 15+ undocumented fields and 3 relationship types.
2 What we learned
For enterprise SaaS platforms undergoing major version changes (v3→v4), official documentation trails the actual API by weeks or months. The reliable source of truth is the API itself — not PDFs, not marketing docs. When building catalog schemas or integration adapters, always validate against live API responses first, then reconcile with official docs second. Auto-research with binary eval criteria is an effective pattern for this kind of reconciliation work.
3 Applies to
- Any future LeanIX integration or schema update — always probe the API first