title: Single backend with multiple APIs
body: <p>I have a single backend defined, for this example named <code>myserver</code> with a runtime url <code>https://myserver.com</code>. Also, I have &quot;Authorization credentials&quot; set for this backend:
  The header <code>x-custom-header</code> is added with a secret value. Every request needs to provide this header.</p>
  <p>My backend provides the following endpoints:</p>
  <pre><code>GET https://myserver.com/Devices
  GET https://myserver.com/Devices/device-1
  POST https://myserver.com/Devices
  Get https://myserver.com/Weather?location=Vienna
  ...
  </code></pre>
  <p>Here comes the problem:
  I want to provide multiple APIs specific for the data:</p>
  <ul>
  <li>Devices Api with API URL suffix <code>Devices</code>:
  <ul>
  <li><code>https://mycompany-apim.azure-api.net/Devices</code></li>
  </ul>
  </li>
  <li>Weather Api with API URL suffix <code>Weather</code>:
  <ul>
  <li><code>https://mycompany-apim.azure-api.net/Weather</code></li>
  </ul>
  </li>
  </ul>
  <p>For some reason, I don't understand how I can achieve that with only a single backend without too much configuration hassle. I have configured <code>&lt;set-backend-service backend-id=&quot;myserver&quot; /&gt;</code> but that obviously does not correctly resolve <code>https://mycompany-apim.azure-api.net/Devices</code> to <code>GET https://myserver.com/Devices</code> but only to <code>GET https://myserver.com/</code>.</p>
  <p>Some solutions that might work:</p>
  <ul>
  <li>Define a backend for each API. E.g. backend <code>myserver-devices</code> with the base url <code>https://myserver.com/Devices</code>
  <ul>
  <li>Problem: I don't want to have X backends configured the same way just with a different url ending.</li>
  </ul>
  </li>
  <li>Configure an <code>rewrite-uri</code> policy for each endpoint in each API.
  <ul>
  <li>Problem: Obviously, this would be even more configuration overhead.</li>
  </ul>
  </li>
  </ul>
  <p><strong>Are there alternatives?</strong></p>