tl;dv · Authentication Profile

Tl Dv Authentication

Authentication

tl;dv 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).

CompanyArtificial IntelligenceMeetingsTranscriptionNote TakingConversation IntelligenceProductivityVideoWebhook

Methods: apiKey, oauth2 Schemes: 2 OAuth flows: authorizationCode API key in: header

Security Schemes

ApiKeyAuth apiKey

· in: header (x-api-key)

MCPOAuth oauth2

· flows: authorizationCode

Source

Authentication Profile

generated: '2026-08-14'
method: searched
source: https://doc.tldv.io
docs: https://doc.tldv.io
summary:
  types: [apiKey, oauth2]
  api_key_in: [header]
  api_key_names: [x-api-key]
  oauth2_flows: [authorizationCode]
  note: >
    Two DIFFERENT auth models on two different surfaces. The REST API is
    api-key only. The hosted MCP endpoint added on 2026-08-14 is OAuth 2.1
    against a Keycloak realm. They are not interchangeable: an x-api-key will
    not authenticate mcp.tldv.io, and an OAuth token will not authenticate
    pasta.tldv.io.
schemes:
  - name: ApiKeyAuth
    type: apiKey
    in: header
    parameter: x-api-key
    description: >
      All requests authenticate with an API key sent on the x-api-key header.
      Keys are issued per user from tl;dv account settings and can be scoped to
      user, team, or organization context.
    key_management_url: https://tldv.io/app/settings/personal-settings/api-keys
    sources: [openapi/tl-dv-openapi.yml]
    surface: rest
    plan_requirement: Business or Enterprise tl;dv account
    plan_requirement_source: https://github.com/tldv-public/tldv-mcp-server
  - name: MCPOAuth
    type: oauth2
    surface: mcp
    method: probed
    description: >
      The hosted MCP endpoint https://mcp.tldv.io/mcp is protected by OAuth 2.1
      with PKCE (S256) against a Keycloak realm, advertised via RFC 9728
      protected-resource metadata and RFC 8414 authorization-server metadata.
      Discovered by probe on 2026-08-14; not documented by tl;dv anywhere.
      Dynamic client registration is open. A single coarse scope, mcp:tools,
      grants every tool.
    issuer: https://keycloak.tldv.io/realms/mcp.tldv.io
    flows:
      - flow: authorizationCode
        authorizationUrl: https://keycloak.tldv.io/realms/mcp.tldv.io/protocol/openid-connect/auth
        tokenUrl: https://keycloak.tldv.io/realms/mcp.tldv.io/protocol/openid-connect/token
        scopes: [mcp:tools]
    pkce: S256
    dynamic_client_registration: https://keycloak.tldv.io/realms/mcp.tldv.io/clients-registrations/openid-connect
    sources:
      - well-known/tl-dv-oauth-protected-resource.json
      - well-known/tl-dv-oauth-authorization-server.json
    see: scopes/tl-dv-scopes.yml
notes: >
  The REST API uses a single API-key model with no scope surface. An OAuth2
  scope surface DOES exist, but only on the hosted MCP endpoint, so
  scopes/tl-dv-scopes.yml is scoped to that surface. Health check (GET
  /v1alpha1/health) is the only unauthenticated REST operation; it was probed
  anonymously on 2026-08-14 and returned 200 {"status":"ok"}. API access
  requires a Business or Enterprise account regardless of surface.

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/tl-dv-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.