Discover B parties (accounts) that are instantly connectable for a given service
The V2 GET /accounts use a property "discoverable" to allow a customer to indicate that they are opted-in/out of being visible to other customers for requesting an inbound connection. The idea being that a customer that wishes to connect to a possible B-side they can should be able to see all discoverable accounts in their /accounts collection.
However, this does not consider the following use cases:
- The presence of the account in a particular location / network for connection. E.g. e.g. INXN is in LON1 and would not want to discover LINX customers who are on LON2 and not LON1, to present in a UI.
- Does not cater for business rules restricting which customers can be reached which vary by product (for example, at Interxion we are only allowing P2P services between different metro networks, and based on a whitelist).
- Whether the B-account has necessary pre-requisites installed. For example, to join a P2P service the b-side must have available connections. This is more of an issue as we add non-connection based services (e.g. #35).
There is a difference between discoverability of the account (i.e. visibility of the account) and discoverability of whether I as an A-side can connect to them as a potential B-side for a specific service. The latter is what we need in V2.
Edited by Mustafa Arif