¶ Routing & APIs Domain
The Routing & APIs domain governs how external systems connect to Fuse via APIs, webhooks, and protocol-based endpoints.
It defines how Fuse exposes entry points — including HTTP routes, WebSocket connections, and webhook listeners — and how access to those routes is secured, scoped, and extended.
Unlike orchestration or messaging within Fuse, this domain handles external interoperability — where third-party systems need to invoke, receive, or integrate with Fuse logic.
Routing & APIs in Fuse supports:
- Runtime registration of custom routes
- Secure API gateway behavior with scoped tokens
- Inbound and outbound webhook endpoints
- Multi-protocol integration without custom proxy logic
- HTTP Route Registration — Define endpoints for RESTful access to Fuse functions
- Webhook Support — Register inbound listeners for external triggers
- WebSocket & Event Streaming — Enable long-lived, bi-directional communication
- Token Scoping & Rate Limiting — Secure endpoints with policy-aligned usage control
- Runtime Path Customization — Extend routing dynamically per tenant, domain, or flow
- CORS & Policy Enforcement — Manage origin access and cross-domain interaction
- Gateway Transformation Rules — Normalize inbound requests before orchestration
| Layer |
Routing & APIs Role |
| Integration |
Serve as the external-facing entry point for requests |
| Automation |
Trigger pipelines or flows based on webhooks |
| Orchestration |
Accept inbound requests and dispatch to orchestrated flows |
| Interoperability |
Apply scopes, tokens, and audit to every external call |
This domain is how Fuse meets the outside world.
- A government system posts a citizen application to a secured Fuse endpoint; Fuse routes it to a validation and workflow sequence.
- A webhook triggers a refund re-evaluation workflow after a bank posts a status change.
- An external mobile app interacts with Fuse using scoped API tokens and session-aware authentication.
¶ Extending the Domain
Extend this domain using: