You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/logic-apps/logic-apps-http-endpoint.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -136,17 +136,19 @@ By default, the Request trigger expects a POST request. You can specify a differ
136
136
137
137

138
138
139
-
## Accept parameters in endpoint URL
139
+
<a name="endpoint-url-parameters"></a>
140
140
141
-
When you want your endpoint URL to accept parameter values through the endpoint's URL, you have these options:
141
+
## Pass parameters through endpoint URL
142
+
143
+
When you want to accept parameter values through the endpoint's URL, you have these options:
142
144
143
145
* [Accept values through GET parameters](#get-parameters) or URL parameters.
144
146
145
-
These values are passed as name-value pairs when sending the request to the endpoint's URL. For this option, you need to use the GET method in your Request trigger. In a subsequent action, you can get the parameter values as trigger outputs by using the `triggerOutputs()` function in an expression.
147
+
These values are passed as name-value pairs in the endpoint's URL. For this option, you need to use the GET method in your Request trigger. In a subsequent action, you can get the parameter values as trigger outputs by using the `triggerOutputs()` function in an expression.
146
148
147
149
* [Accept values through a relative path](#relative-path) for parameters in your Request trigger.
148
150
149
-
These values are passed when sending the request to the endpoint's URL. You also need to explicitly [select the method](#select-method) that the trigger expects. In a subsequent action, you can get the parameter values as trigger outputs by referencing those outputs directly.
151
+
These values are passed through a relative path in the endpoint's URL. You also need to explicitly [select the method](#select-method) that the trigger expects. In a subsequent action, you can get the parameter values as trigger outputs by referencing those outputs directly.
150
152
151
153
<a name="get-parameters"></a>
152
154
@@ -395,4 +397,4 @@ To view the JSON definition for the Response action and your logic app's complet
395
397
396
398
## Next steps
397
399
398
-
*[Receive and respond to incoming HTTPS calls by using Azure Logic Apps](../connectors/connectors-native-reqres.md)
400
+
*[Receive and respond to incoming HTTPS calls by using Azure Logic Apps](../connectors/connectors-native-reqres.md)
0 commit comments