# Ip Range for twitch api

**URL:** <https://discuss.dev.twitch.com/t/ip-range-for-twitch-api/18017>\
**Category:** API\
**Created:** [October 2, 2018, 12:14pm UTC](https://discuss.dev.twitch.com/t/ip-range-for-twitch-api/18017 "2018-10-02T12:14:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![LapusanBogdan](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@LapusanBogdan](https://discuss.dev.twitch.com/u/LapusanBogdan)\
**Post date:** [October 2, 2018, 12:14pm UTC](https://discuss.dev.twitch.com/t/ip-range-for-twitch-api/18017/1 "2018-10-02T12:14:43Z")

</div>

Hello,

I’m trying to whitelist the twich api on my testing environments so that I can consume an webhook exposed by Twitch.  
Can someone please share with me the list of ip ranges that twich api is using ?

Thanks in advance  
Best Regards,  
Bogdan.

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [October 2, 2018, 7:11pm UTC](https://discuss.dev.twitch.com/t/ip-range-for-twitch-api/18017/2 "2018-10-02T19:11:34Z")

</div>

Twitch uses AWS.

Which means at any given point it can and will change, as and when more server spin up/down.

I don’t _think_ it’s a static pool, but I’ll poke someone relevant…

That said, it’s the purpose of the secret rather than known IP’s to secure the webhook

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [October 2, 2018, 9:43pm UTC](https://discuss.dev.twitch.com/t/ip-range-for-twitch-api/18017/3 "2018-10-02T21:43:44Z")

</div>

> We don’t, and we’d prefer people use another method like the signature verification using the secret as given by the websub spec

Use the secret for verification, not IP Ranges is the official answer from upstairs

---

<div class="post-metadata">

**Author:** ![Syzuna](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/syzuna/32/3750_2.png) [@Syzuna](https://discuss.dev.twitch.com/u/Syzuna)\
**Post date:** [October 3, 2018, 12:08am UTC](https://discuss.dev.twitch.com/t/ip-range-for-twitch-api/18017/4 "2018-10-03T00:08:51Z")

</div>

I can understand his need for the IP range at some point but in general you are right.  
Some companies may only accept connections from a previously whitelisted IP or IP range or otherwise their firewall servers would block it.

But yeah secrets are the way to go it somehow possible

---

<div class="post-metadata">

**Author:** ![LapusanBogdan](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@LapusanBogdan](https://discuss.dev.twitch.com/u/LapusanBogdan)\
**Post date:** [October 18, 2018, 10:41am UTC](https://discuss.dev.twitch.com/t/ip-range-for-twitch-api/18017/5 "2018-10-18T10:41:36Z")

</div>

Thanks for your help & answer !

---

<div class="post-metadata">

**Author:** ![system](https://d2opxh93rbxzdn.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://discuss.dev.twitch.com/u/system)\
**Post date:** [November 17, 2018, 10:41am UTC](https://discuss.dev.twitch.com/t/ip-range-for-twitch-api/18017/6 "2018-11-17T10:41:40Z")

</div>

Closed on November 17, 2018, 10:41am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.