Description of problem and its consequences

At the moment, Apinf UI allows the user to use any proxy backend path as long as it is unique. However, API Umbrella matches APIs for calls by the matching order field. As a result, calls maybe terminating in a way user is not expecting. As a worst case scenario, they ends up calling a completely different API.

Cons

Need to upgrade the old frontend prefix on API-umbrella side and in platform database

Need to modify UI for proxy backend form where it will explain to users how the frontend prefix will be created

The second option. Implement the additional validate on the uniqueness

Pros

Don't change the current structure or UI

Cons

User have to think up the new frontend prefix, don't be sure that the nex example will be correct

[Issue] (https://github.com/apinf/platform/issues/2032)

Description of problem and its consequences

We need a way link to the analytics data to particular API ID. This allows us to delete the API along with corresponding analytics data. This would also improve our API owner dashboard.

Solution options

Now it can not be resolved on the platform side via particular API ID. It depends on a structure of ElasticSearch index which doesn't support storage of API ID. [Issue] (https://github.com/NREL/api-umbrella/issues/25)

A suggestion is using the frontend prefix.

Pros

After adding namespace for prefix the request path must be unique for using as link

Cons

Need to re-write realisation when ElasticSearch index will include the field for storing API ID.