can I route APIs by version and region in one gateway

Yes — you can route APIs by both version and region in a single API gateway.

Common ways to do it

You can combine routing rules using:

• Path-based routing
  • Example:
    • /v1/us/orders
    • /v2/eu/orders
• Header-based routing
  • Example headers:
    • X-API-Version: 2
    • X-Region: eu-west-1
• Query parameter routing
  • Example:
    • /orders?version=2&region=us
• Host/subdomain routing
  • Example:
    • us-v1.api.example.com
    • eu-v2.api.example.com

Typical gateway behavior

A gateway can inspect multiple request attributes and route accordingly, for example:

1. Check version
2. Check region
3. Send request to the matching backend service

You can also define precedence, like:

• first match on version
• then on region
• then fallback to a default backend

Example rule set

• v1 + us → orders-service-us-v1
• v1 + eu → orders-service-eu-v1
• v2 + us → orders-service-us-v2
• v2 + eu → orders-service-eu-v2

Things to watch out for

• Rule explosion: version × region combinations can grow quickly
• Maintainability: keep routing rules centralized and documented
• Fallbacks: decide what happens if a version or region is missing
• Consistency: make sure clients send version/region in a predictable way

If you want, I can also show you:

1. a sample routing design, or
2. how to do this in a specific gateway like Kong, Apigee, AWS API Gateway, NGINX, or Envoy.