Hey @superboy97, unfortunately this is the only way we can issue a second API key so if there's a use case for someone to have a second key (say a second app) a second account is ok.
You can but you might not want to. If your first key or account gets compromised (or reported for some reason), it's reasonable to not want your second unrelated app be affected.
id like to have different keys for my personal tmdb that syncs with other apps , and im now looking for to create my own app which will redirect users to sync with tmdb , that would be logical to have two different keys , many services allow this , its not that out of this world
superboy97님의 댓글
11월 1, 2021 at 12:05 오후
No. Why do you think that you need a second one ?
Duplicate accounts are not allowed.
Travis Bell님의 댓글
11월 1, 2021 at 1:26 오후
Hey @superboy97, unfortunately this is the only way we can issue a second API key so if there's a use case for someone to have a second key (say a second app) a second account is ok.
superboy97님의 댓글
11월 1, 2021 at 1:29 오후
Can't we use the same API key for 2 applications ?
Travis Bell님의 댓글
11월 1, 2021 at 1:32 오후
You can but you might not want to. If your first key or account gets compromised (or reported for some reason), it's reasonable to not want your second unrelated app be affected.
XeiDaMoKa님의 댓글
2월 19, 2025 at 5:09 오후
id like to have different keys for my personal tmdb that syncs with other apps , and im now looking for to create my own app which will redirect users to sync with tmdb , that would be logical to have two different keys , many services allow this , its not that out of this world