Using an API key for v1?

A place for developers to advertise their TheTVDB.com enabled app and get help from other developers with the API.
jellyfin
Posts: 2
Joined: Wed Jan 16, 2019 11:20 am

Using an API key for v1?

Postby jellyfin » Wed Jan 16, 2019 11:25 am

Hello all, I'm Joshua representing the Jellyfin project (https://github.com/jellyfin/jellyfin).

In short, we're a free software-focused fork of Emby.

A week ago, we replaced the Emby API keys which were baked into their codebase with new keys we generated. However, it looks like their setup is using the V1 API. I, stupidly, made a major release with our new key but with no other code change, which now doesn't work since it appears to be for V2 only.

Is there any way to fix this up, and allow a newly-generated key access to the old API? We'd work to replace this in future, but I'm hoping there's a quick fix for today just to reenable functionality with our current API key so things "just work" as they were.

Thanks and appreciate your work!

jellyfin
Posts: 2
Joined: Wed Jan 16, 2019 11:20 am

Re: Using an API key for v1?

Postby jellyfin » Wed Jan 16, 2019 11:45 am

We're tracking replacement in an issue on our side (https://github.com/jellyfin/jellyfin/issues/595) just as an FYI, so if we do enable v1 support it would only be temporary until our next release.