Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Currently I have the following resource:
/api/user/12
returns information about user with id=12
/api/user/12/trips
returns a list of trips made by user 12 and their information
However I consider /trip/ a separate resource, so this would continue like this:
/api/trip/5
returns information about trip with id=5
Is this a good way to do this?
You should always use plural to name resources:
Meaning: all users (collection).
Meaning: user 12.
For nested resources related to a given resource, you can do:
Meaning: all
tripsforuser12.But, you still can describe a specific
tripusing this URI:Meaning: trip 5.