Skip to content

Commit 5689599

Browse files
authored
Update call-automation.md
about callback event, best practice is to responde with http status code
1 parent 6be0907 commit 5689599

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/communication-services/concepts/call-automation/call-automation.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -185,6 +185,8 @@ The Call Automation events are sent to the web hook callback URI specified when
185185

186186
To understand which events are published for different actions, refer to [this guide](../../how-tos/call-automation/actions-for-call-control.md) that provides code samples and sequence diagrams for various call control flows.
187187

188+
When acknowledging callback events, it's best practice to respond with standard HTTP status codes like 200 OK. Detailed information is unnecessary and is more suitable for your debugging processes.
189+
188190
To learn how to secure the callback event delivery, refer to [this guide](../../how-tos/call-automation/secure-webhook-endpoint.md).
189191

190192
### Operation Callback Uri

0 commit comments

Comments
 (0)