Emby · Authentication Profile

Emby Authentication

Authentication

Emby supports two authentication mechanisms: User authentication using a custom Authorization header and an access token returned after login, and API‑Key authentication using a static token.

Emby declares 4 security scheme(s) across its OpenAPI definitions.

Media ServerPersonal MediaStreamingVideo LibraryMusic LibraryLive TV

Methods: Schemes: 4 OAuth flows: API key in:

Security Schemes

User Authorization Header other

User Access Token other

API Key Header apiKey

API Key Query apiKey

Source

Authentication Profile

generated: '2026-10-28'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://dev.emby.media/doc/restapi/User-Authentication.html
sources:
- https://dev.emby.media/doc/restapi/User-Authentication.html
- https://dev.emby.media/doc/restapi/API-Key-Authentication.html
description: 'Emby supports two authentication mechanisms: User authentication using a custom Authorization header and an access token returned
  after login, and API‑Key authentication using a static token.'
schemes:
- type: other
  name: User Authorization Header
  evidence: 'Add the following request header on every request: Authorization=Emby UserId="e8837bc1-ad67-520e-8cd2-f629e3155721", Client="Android",
    Device="Samsung Galaxy SIII", DeviceId="xxx", Version="1.0.0.0"'
  location: header
  header: Authorization
  how_to_obtain: Obtain the UserId, Client, Device, DeviceId and Version values from the logged‑in user and client application, then include them
    in the Authorization header as shown.
- type: other
  name: User Access Token
  evidence: The return result object will have an AccessToken property. This should be included in all subsequent Http requests using the header
    X-Emby-Token.
  location: header
  header: X-Emby-Token
  token_url: /Users/AuthenticateByName
  how_to_obtain: Call /Users/AuthenticateByName with the username and password (pw in request body). The response contains an AccessToken which
    is then sent in the X-Emby-Token header.
- type: apiKey
  name: API Key Header
  evidence: Send the API key string in an http request heaser named X-Emby-Token.
  location: header
  header: X-Emby-Token
  how_to_obtain: Create an API key in the Emby Server Dashboard under Security and use the generated key as the X-Emby-Token header value.
- type: apiKey
  name: API Key Query
  evidence: 'An even easier method is to transmit the API key as a query string parameter name api_key . Example: http://localhost:8096/emby/System/Info?api_key=123456789987654321'
  location: query
  how_to_obtain: Create an API key in the Emby Server Dashboard under Security and use the generated key as the value of the api_key query parameter.
docs: https://dev.emby.media/doc/restapi/User-Authentication.html

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/emby-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.