EventCatalog 3.28.0 adds a small but useful flag to services: externalSystem: true. Set it on any service (like Stripe, Twilio, or Snowflake) and EventCatalog will treat it as a third-party dependency rather than something your team owns.
Understanding who owns an API is useful. Understanding who consumes it is what makes the documentation actually actionable.
The EventCatalog OpenAPI generator has always let you document the services that produce your APIs. Today it can also document the downstream services that consume them, with fine-grained control over which routes each consumer receives.
EventCatalog now indexes every field from every message schema in your architecture and makes them searchable, traceable, and verifiable, all from a single page.
This is Schema Insights, available now at /schemas/fields in EventCatalog.
EventCatalog 3.24.0 adds a new optional capability: field-level usage tracking. You can now document which specific fields each consuming service depends on, and see that information surfaced directly on the message page.