Skip to content

Commit 22d718d

Browse files
Add using route parameters section
1 parent cda589b commit 22d718d

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

articles/azure-functions/functions-bindings-http-webhook.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -676,6 +676,24 @@ By default, all function routes are prefixed with *api*. You can also customize
676676
}
677677
```
678678

679+
### Using route parameters
680+
681+
Route parameters defined a function's `route` pattern are available to each binding. For example, if you have a route defined as `"route": "products/{id}"` then a table storage binding can use the value of the `{id}` parameter in the binding configuration.
682+
683+
The following configuration shows how the `{id}` parameter is passed to the binding's `rowKey`.
684+
685+
```json
686+
{
687+
"type": "table",
688+
"direction": "in",
689+
"name": "product",
690+
"partitionKey": "products",
691+
"tableName": "products",
692+
"rowKey": "{id}"
693+
}
694+
```
695+
696+
679697
### Working with client identities
680698

681699
If your function app is using [App Service Authentication / Authorization](../app-service/overview-authentication-authorization.md), you can view information about authenticated clients from your code. This information is available as [request headers injected by the platform](../app-service/app-service-authentication-how-to.md#access-user-claims).

0 commit comments

Comments
 (0)