Hi devs,

Currently, AMS provides two sets of HTTP APIs. One set is used by the
frontend component Dashboard, while the other set serves as the Open API
for other ecosystem dependencies. These two sets of APIs have different
prefixes, but many of their definitions and backend implementations are
actually the same.

Maintaining two sets of APIs will require additional maintenance work.
Therefore, I am wondering if we can unify and use a single set of APIs that
can meet the requirements of both the Dashboard and the ecosystem.

I am open to hearing your thoughts.

Best,
Jinsong

Reply via email to