I'm excited to announce that EventCatalog now supports Attachments - a powerful new feature that allows you to link external resources, diagrams, and documentation directly to your domains, services, events, commands, queries, and channels.
Many teams and organizations have information scattered across different tools and platforms. This makes it difficult to find the information you need when you need it.
With Attachments, you can now link to external resources, diagrams, and documentation directly to your EventCatalog resources.
I'm excited to announce that EventCatalog 2.52.0 introduces a feature: the RemoteSchema component. This new component enables you to fetch and render schemas directly from remote URLs at runtime, ensuring your documentation stays synchronized with your live systems automatically.
For companies managing complex event-driven architectures, keeping documentation in sync with rapidly evolving APIs has always been a challenge. The RemoteSchema component solves this by creating a direct bridge between your live API definitions and your EventCatalog documentation.
The new RemoteSchema component gives you another way to add schemas into your documentation. Providing a URL to a schema will automatically fetch the schema and render it in your documentation.
tip
The RemoteSchema component only works in Server-Side Rendering (SSR) mode. Make sure your EventCatalog is configured to run in SSR mode to use this component. You can read more about how to configure your EventCatalog to run in SSR mode here.
--- id: UserRegistered name: User Registered --- The User Registered event is triggered when a new user signs up for our platform. <!-- Fetch schema from public API --> <RemoteSchemaurl="https://raw.githubusercontent.com/event-catalog/eventcatalog/refs/heads/main/examples/default/domains/E-Commerce/subdomains/Orders/services/InventoryService/events/InventoryAdjusted/schema.json"/>
This simple addition automatically fetches and renders the latest schema from your API, ensuring the documentation always reflects the current state of your system.
The RemoteSchema component creates a direct connection between your live APIs and documentation. When schemas change in your API gateway, schema registry, or service endpoints, your documentation automatically reflects those changes without any manual intervention.
If you prefer to keep your schemas in a single source of truth, you can use the RemoteSchema component to fetch the schema from your API gateway, schema registry, or service endpoints. EventCatalog will automatically fetch the schema and render it in your documentation.
New team members and API consumers can trust that the documentation accurately represents the current API state. This reduces confusion, speeds up onboarding, and improves overall developer productivity.
With support for custom authentication headers and environment variables, the component works seamlessly with private APIs and enterprise security requirements.
Join our Discord to share your use cases and get help from the community
This feature represents a significant step forward in making EventCatalog a living, breathing documentation platform that stays synchronized with your evolving architecture. By connecting directly to your live systems, EventCatalog becomes not just documentation, but a real-time reflection of your event-driven architecture.
The future of API documentation is dynamic, connected, and always current. The RemoteSchema is one step towards that future.