Some options
1) Using a custom header
2) Put something in the query line to confirm only 3) Use a URl action, for example. \ IndividualClient \ 123 \ actions \ Validate \ Invoke {section 19 here http://restfulobjects.files.wordpress.com/2011/11 /restful-objects-spec-052.pdf }
4) Hierarchical URL, for example. \ IndividualClient \ 123 \ Validation
From this post I find this tip
Use POST every time you need to do something with an RPC-like Do use GET for things like computing, if your input is large, in this case use POST
As for your specific question, POST should be used for # 4 and # 5. These operations fall> in accordance with the "RPC-like" guideline above. For # 5, remember that POST does not have to> use Content-Type: application / x-www-form-urlencoded. It could also just be a JSON or CSV payload.
Here is what I am considering:
This is a resource addition:
user / check
Post
Request: UserResource
Answer: ValidationResult
Response codes 200, 400. 404. 500
This is a resource update.
user / 204 / validation
Post
Request: UserResource,
Answer: ValidationResult Answer codes 200, 400. 404. 500
source share