Support for uri-parameters in API endpoints

[mlouro]

Use cases:

• user has oneToMany coupons, and coupons are retrieved via /api/v1/user/{user_id}/coupons
• API endpoint requires a parameter (no GET all), /api/v1/notes/{user_id}/

This can be achieved via query parameters right now, but may not be a fit for everyone and requires a certain type of structure for the API endpoints that may not be possible to change.

[mingfang]

any update on this

[mlouro]

@mingfang unfortunately, no.. I haven't had a need for it, is it something you'd benefit from? what is your exact use-case? Thanks!

[f]

Then we cannot use GitHub API with Amygdala?

Check out: https://api.github.com/

[cryptic-mystic]

+1 to this issue

Certain API queries cannot be easily defined with these schemas. For example, I have the concept of a user group in my application. A group can create their own public facing page on our platform at the endpoint group-slug.myapp.com. So if I need to retrieve a particular group by their slug/subdomain, I would call an endpoint like /groups/subdomain/. From what I can tell I can't really define that query in Amygdala currently.