This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.
Log in to ask a question

api resource naming convention

Posted on 01-24-2018 05:51 PM
Not applicable
Reply posted on --/--/---- --:-- AM

I have two backend services for customer inquiry, one for external clients and one for internal clients. I would like to expose them as two different REST APIs as below. Is this a good naming convention?

https://api.example.com/customerinquiry/v1/customers/external-customerinquiry

https://api.example.com/customerinquiry/v1/customers/internal-customerinquiry

Is this a good approach?

0 13 2,490
Topic Labels
0 Likes
13 REPLIES 13
Top Solution Authors
View all