How can we improve Azure API Management?

Support for parameters in API prefix

Let's say I have root like api.com/trees/{tree-name}. I'd like to have an ability to create Branches API with api.com/trees/{tree-name}/branches/. The only option right now is to keep tree-name in a query.

8 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Dmitry Sevastianov shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
under review  ·  Josh Twist responded  · 

Hi Dmitry, thanks for providing this feedback. Can you help me understand why you’d like this additional feature? Be great to understand why this would improve the product for you.

1 comment

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • Dmitry Sevastianov commented  ·   ·  Flag as inappropriate

    Hi Josh, sure.

    To continue the analogy, say, I have Forest API which is exposed as trees/{tree-name}. Lumberjacks won't be interested in particular branches, I would give them Forest API. Squirrels care about Branches API, which is naturally looks like /trees/{tree-name}/branches/{branch-name}.

    So I'd give them Branches API which by its nature includes Forest API as well, though probably without the ability to DELETE trees.

    I hope it makes sense.

Feedback and Knowledge Base