Resolve "Message part was not recognized" in the API Gateway

Home > Search
  by

This event will appear in the response tab of the API Gateway audit log.

This error will identify the policy and operation that has a message part that is not being recognized. In this example, the policy is /application/example, and the operation is myOperation. Right-click on the service, select Service Properties, select the WSDL tab, select Reset WSDL, copy the WSDL URL, and select Cancel twice. Paste the WSDL URL into a web browser, and then use Ctrl + F and search for the operation that is not recognized. The objective here is to first verify that the operation exists in the WSDL. If the operation is not in the WSDL, have the developer provide you with an updated WSDL that contains the message part. If the message part in the WSDL is malformed, have the developer provide you with an updated WSDL with a properly formatted message part.

<message name="myOperationInput">
  <part element="tns:CreateContractRequest" name="myOperationRequest"/>
</message>

 

It is entirely possible that the message part is in the WSDL and is properly formatted. In this scenario, there may some problem with one of the other operations in the WSDL. Check the API Gateway audit logs for events indicating a problem with one of the other operations in the WSDL.



Add a Comment




We will never share your name or email with anyone. Enter your email if you would like to be notified when we respond to your comment.




Please enter in the box below so that we can be sure you are a human.




Comments