Inth · Authentication Profile

Inth Authentication

Authentication

The c15t consent backend authenticates server-side requests with a Bearer API key. Browser-facing endpoints (init, status) are public and unauthenticated so the client SDK can bootstrap a banner without exposing a secret.

Inth declares 1 security scheme(s) across its OpenAPI definitions.

CompanyConsent ManagementPrivacyCookie ConsentGDPRCCPAComplianceConsentDeveloper ToolsOpen Source
Methods: Schemes: 1 OAuth flows: API key in:

Security Schemes

http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-19'
method: searched
source: >-
  github.com/c15t/c15t packages/backend/src/middleware/auth/validate-api-key.ts
  and c15t.com/docs/self-host. Auth profile derived from the open-source backend
  and confirmed against docs.
description: >-
  The c15t consent backend authenticates server-side requests with a Bearer API
  key. Browser-facing endpoints (init, status) are public and unauthenticated so
  the client SDK can bootstrap a banner without exposing a secret.
docs: https://c15t.com/docs/self-host
schemes:
  - id: bearerAuth
    type: http
    scheme: bearer
    location: header
    header: Authorization
    format: "Bearer [example key]<key>"
    description: >-
      Secret API key passed as a Bearer token. Keys are provisioned per instance
      (inth.com dashboard) or configured for self-hosted deployments. The
      extractBearerToken middleware requires the literal "Bearer " prefix.
    applies_to:
      - GET /subjects (list by external ID)
      - PUT /legal-documents/{type}/current
public_endpoints:
  - GET /init
  - GET /status
  - GET /spec.json
oauth2: false
openid_connect: false
mutual_tls: false