Web API Activity could use a few updates with clarity

Feedback Documentation
,
1

Hello,

Some of the attributes of this activity below could use some updates with clarifications. I hope I am not missing something.

For example: the ACCEPT feature and BodyFormat attributes require a bit of elaboration.

I see that it is possible for “signed” API requests to fail under the following conditions.

if a header of type “Accept” is explicitly added to the headers collection instead of setting ACCEPT to JSON (for instance)
Similarly, adding “Content-Type” header to the headers collection instead of setting it in the BodyFormat property.

In this case, if I code the HttpClient in C#, and I add the Content-Type to the request headers instead of the Content body, the request fails with a “misused header” exception.

It is not very clear what the values of the BodyFormat attribute must be. Maybe I haven’t looked, but a link to a related documentation would be helpful.

Therefore, the documentation of this activity does not clarify some of these scenarios.

Thanks!