Try using the auto-generated one. I think you are encountering this issue because it is looking for specific flow name which the auto-generated one is doing.
I suggest you try this approach with your RAML.
Do you have RAML for this? Did you create the flow with the auto-generated feature using RAML? You are getting this issue because the url you are calling is not registered with the Apikit Router.
Hi @ryanandal I did not used the auto-generated, I created my self. I can see in console my API definition, and it has the method I am using defined.
org.mule.module.launcher.DeploymentInitException: MuleRuntimeException: A server in port(8081) already exists for ip(0.0.0.0) or one overlapping it (0.0.0.0).
I think it is because I have another xml listening also on port 8081. So, I have to change the port for this auto generated xml?
Yes, you can change the port for now. 8081 is the default port for auto-generated flow. You can change it afterwards.
@ryanandal I changed the port and now I am not getting the "resource not found" message. But now when I do the request I get on my API Rest a null instead of the parameters passed, and I am passing in the payload all parameters with json. I get a response with 500 status code.
Also if I directly from postman do the same request (with same parameters), but directly to the API, it works well.
Did you check why did you got http status 500? What specific error you encountered on the log? Probably you have issues within the flow.
The 500 error is because my Rest API receive a null instead of the parameters that should receive.
But I have used a "set payload" element in Mule to check that the payload has what it should, and it is right.
I don't know if the problem can be the raml file.