YouTube · Authentication Profile
Youtube Authentication
Authentication
YouTube secures its APIs with apiKey and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).
VideoYouTubeGoogleMediaSocialStreamingLive StreamingChannelsPlaylistsSearch
Methods: apiKey, oauth2
Schemes: 2
OAuth flows: authorizationCode
API key in: query
Security Schemes
OAuth2 oauth2
· flows: authorizationCode
apiKey apiKey
· in: query (key)
Source
Authentication Profile
generated: '2026-11-04'
method: derived
source: openapi/youtube-analytics-groups-api-openapi.yml, openapi/youtube-analytics-reports-api-openapi.yml,
openapi/youtube-captions-api-openapi.yml, openapi/youtube-channels-api-openapi.yml, openapi/youtube-comment-threads-api-openapi.yml,
openapi/youtube-comments-api-openapi.yml, openapi/youtube-group-items-api-openapi.yml, openapi/youtube-groups-api-openapi.yml,
openapi/youtube-i18n-api-openapi.yml, openapi/youtube-jobs-api-openapi.yml, openapi/youtube-live-streams-api-openapi.yml,
openapi/youtube-livebroadcasts-api-openapi.yml ...
summary:
types:
- apiKey
- oauth2
api_key_in:
- query
oauth2_flows:
- authorizationCode
schemes:
- name: OAuth2
type: oauth2
flows:
- flow: authorizationCode
authorizationUrl: https://accounts.google.com/o/oauth2/auth
tokenUrl: https://oauth2.googleapis.com/token
scopes: 4
description: OAuth 2.0 authentication for YouTube Analytics API
sources:
- openapi/youtube-analytics-groups-api-openapi.yml
- openapi/youtube-analytics-reports-api-openapi.yml
- openapi/youtube-captions-api-openapi.yml
- openapi/youtube-channels-api-openapi.yml
- openapi/youtube-comment-threads-api-openapi.yml
- openapi/youtube-comments-api-openapi.yml
- openapi/youtube-group-items-api-openapi.yml
- openapi/youtube-groups-api-openapi.yml
- openapi/youtube-i18n-api-openapi.yml
- openapi/youtube-jobs-api-openapi.yml
- openapi/youtube-live-streams-api-openapi.yml
- openapi/youtube-livebroadcasts-api-openapi.yml
- openapi/youtube-livechatmessages-api-openapi.yml
- openapi/youtube-livechatmoderators-api-openapi.yml
- openapi/youtube-playlist-items-api-openapi.yml
- openapi/youtube-playlists-api-openapi.yml
- openapi/youtube-report-types-api-openapi.yml
- openapi/youtube-reports-api-openapi.yml
- openapi/youtube-search-api-openapi.yml
- openapi/youtube-subscriptions-api-openapi.yml
- openapi/youtube-videocategories-api-openapi.yml
- openapi/youtube-videos-api-openapi.yml
- name: apiKey
type: apiKey
in: query
parameter: key
sources:
- openapi/youtube-captions-api-openapi.yml
- openapi/youtube-channels-api-openapi.yml
- openapi/youtube-comment-threads-api-openapi.yml
- openapi/youtube-comments-api-openapi.yml
- openapi/youtube-i18n-api-openapi.yml
- openapi/youtube-live-streams-api-openapi.yml
- openapi/youtube-livebroadcasts-api-openapi.yml
- openapi/youtube-livechatmessages-api-openapi.yml
- openapi/youtube-livechatmoderators-api-openapi.yml
- openapi/youtube-playlist-items-api-openapi.yml
- openapi/youtube-playlists-api-openapi.yml
- openapi/youtube-search-api-openapi.yml
- openapi/youtube-subscriptions-api-openapi.yml
- openapi/youtube-videocategories-api-openapi.yml
- openapi/youtube-videos-api-openapi.yml
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/youtube-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.