# Twitch drops in helix API

**URL:** <https://discuss.dev.twitch.com/t/twitch-drops-in-helix-api/27545>\
**Category:** API\
**Created:** [August 6, 2020, 1:29pm UTC](https://discuss.dev.twitch.com/t/twitch-drops-in-helix-api/27545 "2020-08-06T13:29:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dmitriy\_Lohunov](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/dmitriy_lohunov/32/9889_2.png) [@Dmitriy\_Lohunov](https://discuss.dev.twitch.com/u/Dmitriy_Lohunov)\
**Post date:** [August 6, 2020, 1:29pm UTC](https://discuss.dev.twitch.com/t/twitch-drops-in-helix-api/27545/1 "2020-08-06T13:29:51Z")

</div>

Hello! I’m currently developing a backend for integration with Twitch drops. All the drops’ docs, that I was able to find, reference API V5 (kraken) but in the same time it’s specified as deprecated and I should use helix API.  
Am I missing something here or I should just wait until drops will be migrated to the new version?

---

<div class="post-metadata">

**Author:** ![WLG3R](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/wlg3r/32/6985_2.png) [@WLG3R](https://discuss.dev.twitch.com/u/WLG3R)\
**Post date:** [August 6, 2020, 3:19pm UTC](https://discuss.dev.twitch.com/t/twitch-drops-in-helix-api/27545/2 "2020-08-06T15:19:35Z")

</div>

There is no published timeline for migrations. If you need to use it now use kraken. If your campaign isn’t going to run for a while, then you can wait and see.

---

<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:** [September 5, 2020, 3:29pm UTC](https://discuss.dev.twitch.com/t/twitch-drops-in-helix-api/27545/3 "2020-09-05T15:29:49Z")

</div>

Closed on September 5, 2020, 3:29pm UTC

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

---

<div class="post-metadata">

**Author:** ![jbulava](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/jbulava/32/6777_2.png) [@jbulava](https://discuss.dev.twitch.com/u/jbulava)\
**Post date:** [September 10, 2020, 7:48pm UTC](https://discuss.dev.twitch.com/t/twitch-drops-in-helix-api/27545/4 "2020-09-10T19:48:19Z")

</div>

Opened on September 10, 2020, 7:48pm UTC



---

<div class="post-metadata">

**Author:** ![jbulava](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/jbulava/32/6777_2.png) [@jbulava](https://discuss.dev.twitch.com/u/jbulava)\
**Post date:** [September 10, 2020, 7:53pm UTC](https://discuss.dev.twitch.com/t/twitch-drops-in-helix-api/27545/5 "2020-09-10T19:53:25Z")

</div>

Thanks, @WLG3R! I would agree with this advice and wanted to confirm this approach. We [launched the newest version of Drops](https://discuss.dev.twitch.com/t/announcing-a-new-version-of-drops-for-game-developers/27771) on August 18 that will outlast V5.

As mentioned in that announcement, the past version of Drops will be available into January 2021. If your campaign ends before this time, feel free to use either version. If your campaign will extend beyond January 2021, you should use the newest version of Drops to avoid duplicate work or disruption during the campaign.