supporting-multiple-cf-instances.html.md.erb

---
title: Supporting multiple instances
owner: Core Services
---


You can register your service broker with multiple <%= vars.app_runtime_first %> instances.

It might be necessary for the broker to know which <%= vars.app_runtime_abbr %> instance is making a given request. For example, when using [Dashboard Single Sign-on](dashboard-sso.html), the broker is expected to interact with the authorization and token endpoints for a given <%= vars.app_runtime_abbr %> instance.

There are two strategies that can be used to discover which <%= vars.app_runtime_abbr %> instance is making a given request.


## <a id='routing-auth'></a> Routing and authentication

The broker can use unique credentials, a unique URL, or both for each <%= vars.app_runtime_abbr %> instance. When registering the broker, you can configure different <%= vars.app_runtime_abbr %> instances to use different base URLs that include a unique ID. For example:

* On <%= vars.app_runtime_abbr %> instance 1, the service broker is registered with the URL `broker.example.com/123`.

* On <%= vars.app_runtime_abbr %> instance 2, the service broker is registered with the URL `broker.example.com/456`.


## <a id='x-api-info-location'></a> X-Api-Info-Location header

All calls to the broker from <%= vars.app_runtime_abbr %> include an `X-Api-Info-Location` header containing the `/v2/info` URL for that instance. The `/v2/info` endpoint returns further information, including the location of that <%= vars.app_runtime_abbr %> instance's UAA.

Support for this header was introduced in cf-release v212.