Push Webhook

LAST EDIT Jul 21 2021

Using the Push webhook, you can receive payloads of all events from your application. When configured, every event in the Chat application will propagate to your webhook endpoint. The complete list of supported events can be found on Events page.

Use-cases

Copied!

Push webhooks are useful when you want your server application to be in sync with the chat. Here are some examples:

  • Implementing a complex notification system (e.g. involving SMS and/or e-mail)

  • Migration from a different chat provider to Stream Chat without disruption

  • User activity monitoring

Request format

Copied!

Your endpoint will receive a POST request with a JSON encoded body containing the event and all corresponding fields:

See more payload examples on Events page.

Performance and Error Handling

Copied!

In case of the request failure Stream Chat attempts to retry a request. The amount of maximum attempts depends on the kind of the error it receives:

  • Response code is 408, 429 or >=500: 3 attempts

  • Network error: 2 attempts

  • Request timeout: 3 attempts

The timeout of one request is 6 seconds, and the request with all retries cannot exceed the duration of 15 seconds.

Whitelisting Stream Domains

Copied!

US-East

Az

eip

Primary

us-east-1b

34.225.10.29/32

Secondary

us-east-1c

34.198.125.61/32

Tertiary

us-east-1e

52.22.78.160/32

Quaternary

us-east-1d

3.215.161.238/32

EU-west

Az

eip

Primary

eu-west-1a

52.212.14.212/32

Secondary

eu-west-1b

52.17.43.232/32

Tertiary

eu-west-1c

34.241.110.177/32

Sydney

az

eip

Primary

ap-southeast-2a

54.252.193.245/32

Secondary

ap-southeast-2b

13.55.254.141/32

Tertiary

ap-southeast-2c

3.24.48.104/32

mumbai

az

eip

Primary

ap-south-1a

65.1.48.87/32

Secondary

ap-south-1b

15.206.221.25/32

Tertiary

ap-south-1c

13.233.48.78/32

Singapore

az

eip

Primary

ap-southeast-1a

13.229.11.158/32

Secondary

ap-southeast-1b

52.74.225.150/32

Tertiary

ap-southeast-1c

52.76.180.70/32