Your APIs can work with multiple backends and
route calls to them based on different headers, REST resources, or even parameter values. Today we are expanding this functionality to routing based on multiple gateway URLs so the same API can, for example, serve production, development, and test environments picking the appropriate one based on the URL used for the invocation.
Typically, all your APIs share the same base URL of the gateway that you can
set to a particular custom URL of your choice such as
apis.example.com.
Also, starting with the
Medium plan, API Cloud allows you to have multiple gateways. This is typically used by API publishers who want to have separate API gateways for different regions (for example,
us.apis.example.com, eu.apis.example.com,
apac.apis.example.com).
That same functionality can now be used within the same physical gateway to provide different URLs for different backend environments such as
prod.apis.example.com,
dev.apis.example.com, and
qa.apis.example.com. In that case, you can assign them all to the same API gateway and then use the Dynamic Endpoint type to route the calls to the corresponding backend environments based on the URL used by the caller.
