Mgiyuk

REST API naming convention Best Practice for create or update a resource In my application, a client can create resources for which we compute our ID and assign it to the resource. However a client can also reference, for every resource, a specific ID it wants to use (we call it external ID) so that we do not force the client to only use our IDs. We then have the following endpoints: We would like to allow a client to update a resource with its external ID. We thought about Would you have an idea for a better name in lines with REST best practices? Maybe PUT /resources/{the-id}?id-type={external|internal} ? – sp00m Jun 29 at 9:31 PUT /resources/{the-id}?id-type={external|internal} "Best practices" would state that you shouldn't use verbs like create or update within your UR...