Issue with Request Bodies Not Being Reflected in the DELETE Method of Web Service DataAction

[tomoki.koike]

Issue
When using the DELETE method in DataAction of GenesysCloud, the content of the request body is called by API as NULL.

Assumption
You want to make an API call to a WebService using DataAction.
The API uses the DELETE method and requires a request body.
When the above API was executed from the Test tab of DataAction, an Error was displayed indicating that the request body was null.
Also, when checking the log on the API side, we confirmed that the Log was called with the request body null.

Situation
Configure the following settings and make an API call from the TEST tab
Configuration

{
“requestUrlTemplate": ”https://9xxx.execute-api.ap-southeast-1.amazonaws.com/dev/holders/${input.partyId}/policies/${input.
“requestType": ‘DELETE’, }
“headers": {
“accept": ‘application/json’, ‘headers’: {
“Authorization": ”Bearer ${input.token}”
},.
“requestTemplate“: ‘{\n \’receptionNos\”: [\n \“${input.receptionNo}\”\n ]\n}”
}

Test Result
Error occurs where the request body is null
Checking the Log on the API side, it was confirmed that Body was called with Null

Inference
Checking the log at the time of TEST execution from the web console log, it appears that Result is null when creating the request body, is this a specification of DataAction of GenesysCloud?

  {
       “step": 6,.
       “name": ‘Resolve request body template’,.
       “success": true, ‘result’: ”
       “result": ””
   }, }

I would like to know how to solve this problem.

[vpirat]

Hi,

This sounds consistent with HTTP specs:

The DELETE method has no defined semantics for the message body, so this should be empty.

See DELETE - HTTP | MDN
So I would say this is the expected behavior.

Regards,
V.P.

[tomoki.koike]

Thanks for sharing the information!