I am trying to wrap my head around the approach I need to implement YouTube API V3 on my website, I shall describe the scenario:
I have a 'Platform' which enables users to create a 'Channel' and manage streamed content:
theplatform.com
When they create the 'channel' on the 'platform', they can provide their own URL, so:
mychannel.com is 'theplatform.com' under the hood
mychannel.com needs to publish and manage content on youtube.com/mychannel
I only want to create the Google Developer Project 'ThePlatform' once under the 'theplatform' google account
Channel owners need to 'connect' their YouTube channel to their 'mychannel.com' website without knowing about Google Developer Consoles (they are business users, not API developers)
If possible, when performing the OAuth, they should go to mychannel.com/oauth instead of theplatform.com/oauth,
- unfortunately the OAuth settings seem to require set URLs for redirection, this would mean I would need to update the 'ThePlatform' API key settings for each new 'channel' before they could connect
The API Key for ThePlatform project will be hard-coded into theplatform.com and will be the same for mychannel.com, and by setting their YouTube Channel account on mychannel.com, theplatform.com's code knows it is interacting with the correct YouTube channel.
Does that make sense?
This is in PHP. I am using the PHP composer API.
I am happy for the 'ThePlatform' project to handle request quota, as I don't want to set up and manage a new project per 'channel' and will be charging 'channels' to cover costs.
If anyone gets what I am talking about here and knows the 'philosophy' and 'approach' I need to take I would love some advice. I am a developer on my own trying to start up, you guys may be my only help!
- In the meantime I will plug away, if I come to a solution down the road I shall answer my own question for future developers. Thank you.