Acts as a trigger and listens for HTTP requests on a configured endpoint. When a call is received on the configured endpoint, it triggers a new instance of the flow and passes the data received in the request to the flow for processing. It can also be configured to automatically respond to the incoming request when the flow has started, or let you construct a response based on the flow execution and send a response to the caller.
When you create the HttpListener, change the default name to a custom name, otherwise you can’t store the Http Listener. Also, when clicking package settings you can specify whether you want to send a response immediately. In the first case I didn’t send an immediate response, but returned the result of the schema validation. That makes sense obviously.
To find the URL to post to klik on the link under Host. Now you see an URL that starts with http.
If you want to use the URL from Postman, don’t forget to change http to https. Also, a relative URL can be appended to the end of the URL. The relative URL is specified when adding the HTTP Listener to a Logic App. Below is the configuration of a HTTP Listener in a Logic App after you have clicked Edit Action:
Lastly, you need to set the security settings of the API App to Public (Anonymous) to allow external clients to access the end point. This setting is available under “All settings > Application Settings” of the HTTP Listener API App.
More information: HTTP Listener
Think * Share * Integrate 