Okapi Okapi

GET /helix/users/follows → endpoint removal

Twitch API

Stopped working

On September 6, 2023, the GET /helix/users/follows endpoint was permanently removed. Requests made to this endpoint fail. The change affects all clients calling this specific Twitch API route.


Calls it hits

  • GET /helix/users/follows

What to use instead of these calls

Use Get Followed Channels (GET /helix/channels/followed) or Get Channel Followers (GET /helix/channels/followers) instead.

In Twitch API's words

The Get Users Follows API endpoint has been removed.

Twitch API, Announcement

Facts

API
Twitch API api.twitch.tv
Kind
Endpoint removal
Announced
February 22, 2023
Takes effect
September 6, 2023
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Twitch API's own pages

Questions

When does this change take effect?

Calls to GET /helix/users/follows on Twitch API stopped working on September 6, 2023.

What happens to calls after September 6, 2023?

They have failed since September 6, 2023.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.


More from Twitch API 6

  1. /helix/entitlements/codesEndpoint removal Stopped working
  2. PUT /helix/streams/tagsEndpoint removal Stopped working
  3. GET /helix/streams/tagsEndpoint removal Stopped working
  4. GET /helix/tags/streamsEndpoint removal Stopped working
  5. GET /helix/soundtrack/*Endpoint removal Stopped working
  6. GET /helix/hypetrain/eventsEndpoint removal Stopped working

You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub