Add optional parameters for OAuth client ID and secret to setup #688
Conversation
Use your own Google API client ID and client secret in setup by calling ytmusicapi oauth --client_id <your Google API client ID> --client_secret <your Google API client secret> to avoid HTTP 400: Bad Request errors
There was a problem hiding this comment.
Thank you for for figuring this out and submitting the PR. However, there are still some more improvements needed:
- The argparse args you added apply to both setup types, although they don't matter for the
browseroption. This will lead to a misleading CLI (i.e. try running ytmusicapi browser --help). They should only apply to the oauth option. Since the interface is interactive anyway you could also circumvent this by interactively asking for TV auth (deprecated) or client id/secret (recommended) - then request all the info viainput(). Both solutions are valid imo. - Deprecate the current TV oauth docs and include info on how it should be done currently. This would mean adding guidance on how to correctly create the ID/Secret via Google Cloud. Could be done in a separate PR
|
nevermind, it does seem to work with that configuration |
- Add subparsers for parameters for oauth and browser tokens - Add help options - Add a check for presence of both client_id and client_secret if oauth is chosen.
|
Hi |
Use your own Google API client ID and client secret in setup by calling
ytmusicapi oauth --client_id <your Google API client ID> --client_secret <your Google API client secret>to avoid HTTP 400: Bad Request errors (issue #679 )See developers.google.com/youtube/registering_an_application for instructions on how to create your own youtube OAuth credentials.