Sending optional parameters as empty in a web-service requestbody which do not have values

Question

I am trying to consume some rest webservices with json request and response format. I am sending all the values in the request even the optional parameters which do not have values.(The default value for all the optional parameter I set as empty string "" to avoid null). One of my colleague pointed out to check empty parameters for optional values and remove them from the request if no value exist.

I know I would be stupid to ask this very basic question but I would like to know the best practice:

Is it good to send empty parameters or we need to check for empty parameters and send only the one which has value.

score 0 · Answer 1 · edited May 23 '17 at 12:02

0

Generally the best practise is to follow the API. But if removing optional parameters which do not have values does not affect the target consumers of the API, then you can go for it.

You can check the answer to following post, to get some good reasons to keep the null fields.

Is it Worth To exclude null Fields.

edited May 23 '17 at 12:02

Community

1
1

answered Mar 25 '17 at 18:40

Shailesh Yadav

1,061
1
15
30

Sorry if the question is confusing but the question is about a request and not response. – Prakruti Pathik Mar 25 '17 at 20:21
doesnt matter, if its request or response best practise is to follow API, and keep the request or response fields intact. – Shailesh Yadav Mar 28 '17 at 15:41

Sending optional parameters as empty in a web-service requestbody which do not have values

1 Answers1