splitting proxy by app parameters

[s12312731723]

I am looking for a solution and not sure how to handle this

we want to use a single proxy to be able to serve a set of apis to users, the users would be identified by a flag on there app level e.g developer.app.userName,  each user has a limited set of apis from the suite and also gets there own app engine (target).

for example

• User1 may have access to 3/10 apis on there engine. e.g:

1.   /v1/user -> {user1 target}/v1/user/access
2. {user1 target}/v1/user/refresh
3. {user1 target}/v1/user/logout

• User2 may have access to 1 api on there engine. e.g:

1.  - e.g /v1/user -> {user2 target}/v1/user/getDetails

if I write a proxy endpoint and code all apis into the flow this then becomes a nightmare visually to see which user has access to which endpoints. and having to add if statements to determine which apis they have access to on the routing rules.

there seems to be a solution to use proxy chaining, but using multiple proxy endpoints however occurs a double quota for using the default proxy as a load balancer

e.g

Proxy Endpoint

default -> check token and append /user1 /user2 to the path and call the proxy

essentially we would prefer to just route from ProxyEndpoints /default to /user1 router without a double quota cost, leading to very clean documentation of the proxy in this way of having seperated flows per user

is there anything else that can do this in a clean way that I may not have considered or a way to get around the double quota issue

Thanks