how would you guys structure your REST endpoints with ktor and locationsAPI when the same object can be retrieved by different keys? so i have as an example /api/articles/{id} (id is an UUID) but the same article can be fetched by it's unique name. would you prefer something like /api/articles/by-name/{name} or /api/articles/{name}/by-name or some kind of "polymorphism" where there is a manual check if the parameter is a UUID or a name?

Why is your api designed to have to unique identifier? (UUID and Name)

that's a weird question .. business requires it. it's basically unique synonyms and that's the way the data is.

If those were the only options I would preffer

/api/articles/by-name/{name}

, else

/api/articles?name={name}

i am open for better options 🙂