Skip to content
This repository was archived by the owner on Nov 29, 2023. It is now read-only.

MV-10296 Remove incorrect exclusion to retry policy #1157

Merged
tpensyl merged 3 commits into from
Sep 20, 2023
Merged

MV-10296 Remove incorrect exclusion to retry policy #1157

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5f96d92
Remove incorrect exclusion to retry policy
tpensyl Sep 19, 2023
9f35714
MV-6709
tpensyl Sep 19, 2023
b08747b
MV-10296
tpensyl Sep 19, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion site/docs/messaging/webhooks.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,6 @@ Bandwidth uses HTTP Callbacks webhooks to send events to any publicly addressabl
* All Message callbacks are sent as a list/array `[ {message metadata} ]` to the webhook url in the application.
* You **MUST** Reply with a `HTTP 2xx` status code for _every_ callback/delivery receipt. Bandwidth will retry _every_ callback over the next 24 hours until a `HTTP 2xx` code is received for the callback. After 24 hours, Bandwidth will no longer try to send the callback.
* Bandwidth's Messaging platform has a 10 second timeout for callbacks. This means your server must respond to the callback request within 10 seconds, otherwise the platform will try again at a later time.
* Your server should return a response smaller than 16kB. If the reponse is larger, Bandwidth will not retry the callback.
* Because we guarantee "at least once delivery" of events, it is possible (but not common) to receive duplicate message events. Your server should be able to handle duplicates.

## Inbound Message Webhooks
Expand Down