add-orchestrated-route

To add an API gateway route that chains upstream services, you define a config-driven endpoint specifying sequential, parallel, or conditional calls. This approach composes upstream services and response handling consistently without hard-coding path logic.

Config-driven route registration works by extending the config schema to dynamically register new gateway endpoints. This allows you to wire in middleware, orchestration logic, and response transformations declaratively rather than modifying hard-coded gateway paths.

Yes, you can enforce auth and rate limiting without hard-coding by applying middleware integration within the route configuration. The config schema updates allow you to declaratively wire these policies into the new orchestrated endpoint.

The best way to test an orchestrated gateway route is to add unit and integration coverage for success paths, upstream failures, auth failures, and rate-limit behavior. This validates the orchestrator logic and normalized error handling before shipping.

You need to update the config schema to add an API gateway route because the endpoint definition, upstream calls, and middleware are declaratively driven by configuration. This schema update enables dynamic route registration and consistent orchestration logic.