Hello @Mahesh PR - Thanks for reaching out! Are you sending a valid JSON payload with a Content-type: application/json
header? You have defined the JSON schema below in the Request action to match the Body of the incoming request:
"properties": {
"CaptureError": {
"type": "string"
},
"GroupId": {
"type": "string"
},
"GroupName": {
"type": "string"
},
"RunSeq": {
"type": "string"
},
"RunSeqName": {
"type": "string"
}
}
This makes the Request trigger expect the payload in incoming requests to be a data type of JSON along with a Content-type: application/json
header. However, If you're invoking the request with the Content-type: application/json
header but sending a payload that's not a valid JSON, you'll hit the error below:
{
"error": {
"code": "InvalidRequestContent",
"message": "The request content is not valid and could not be deserialized: 'Unexpected character encountered while parsing value: a. Path '', line 0, position 0.'."
}
}
Could you verify if the payload is a valid JSON, and let us know if the issue persists?