@Lily It depends upon how you want to expose the API's to the end user/consumers. There are no drawbacks and you can create the Frontend as per your requirement.
In general for best pratices on designing any API you can refer to this document.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi experts,
I encounter a bunch of APIs like these and not sure what it the better way to map them to APIM.
Same url with different methods, and each of them have different parameters.
POST /customers
GET /customers
PUT /customers
DELETE /customers
For above sample, it seems I can create 4 operations in APIM (create_customers, get_customers, update_customer, delete_customer)
But I'm not sure if this is a good practice for such scenario or any drawbacks will happen in the future.
Can you give me some hints ?
Thank you
@Lily It depends upon how you want to expose the API's to the end user/consumers. There are no drawbacks and you can create the Frontend as per your requirement.
In general for best pratices on designing any API you can refer to this document.