ytapi-dev · Authentication Profile

Ytapi Dev Authentication

Authentication

ytapi-dev declares 2 security scheme(s) across its OpenAPI definitions.

CompanyVideoTranscriptsYouTube
Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

Bearer token http-bearer
X-API-Key apiKey

Source

Authentication Profile

ytapi-dev-authentication.yml Raw ↑ 
generated: '2026-10-31'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.ytapi.dev/authentication/
sources:
- https://docs.ytapi.dev/authentication/
- https://docs.ytapi.dev/agent-setup/
- https://docs.ytapi.dev/
- https://docs.ytapi.dev/agent-setup/
schemes:
- type: http-bearer
  name: Bearer token
  evidence: 'You can authenticate using either standard Bearer token or the X-API-Key header:'
  location: header
  header: Authorization
- type: apiKey
  name: X-API-Key
  evidence: 'You can authenticate using either standard Bearer token or the X-API-Key header:'
  location: header
  header: X-API-Key
note: All authentication uses an API key that is obtained from the YTAPI Developer Dashboard.
docs: https://docs.ytapi.dev/authentication/

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.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/ytapi-dev-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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.