StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POIs it ok to POST/PUT a structure that is different from the one returned?
primarykey
Id
5165051
data
AcceptedAnswerId
5165178
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-03-02T08:27:12.510
FavoriteCount
0
LastActivityDate
2011-03-02T09:09:26.607
LastEditDate
LastEditorUserId
0
OwnerUserId
432859
ParentId
0
PostTypeId
1
Score
0
ViewCount
94
LastEditorDisplayName
text
Body
I am designing a restful web service and have a problem that I foresee will be a common one. Lets say you have a resource url: /users and the GET operation for that url returns a list of users with basic details. Now I want to create a POST operation for users, but in order to create a user I need to pass more information than is returned by /users and any specific user url (users/1 etc). Is this ok? What is the usual approach to this kind of situations?
Tags
<rest>
Title
Is it ok to POST/PUT a structure that is different from the one returned?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPiotr
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.