Trustlogix · Authentication Profile

Trustlogix Authentication

Authentication

Trustlogix secures its APIs with apiKey, oauth2, and openIdConnect across 4 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyData SecurityData Access GovernanceData Security Posture ManagementAccess ControlSnowflakeDatabricksAI SecurityMCPAuthorizationCompliance

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

Security Schemes

ApiKeyAuth apiKey

· in: header ()

SessionLogin http

scheme: custom

MCP-OAuth2 oauth2

SSO-OIDC openIdConnect

Source

Authentication Profile

generated: '2026-07-21'
method: searched
source: https://docs.trustlogix.io/trustlogix-api-documentation.md
docs:
  - https://docs.trustlogix.io/trustlogix-api-documentation.md
  - https://docs.trustlogix.io/integrations/single-sign-on.md
  - https://docs.trustlogix.io/trust-ai/mcp-server.md
summary:
  types: [apiKey, oauth2, openIdConnect]
  api_key_in: [header]
  oauth2_flows: [authorizationCode]
schemes:
  - name: ApiKeyAuth
    type: apiKey
    in: header
    parameter_name: Authorization
    description: >-
      REST API requests authenticate with an API key passed in the Authorization
      header. Most tenant-scoped endpoints additionally require a tenantId header.
    applies_to: TrustLogix REST API (/api/*)
    source: https://docs.trustlogix.io/trustlogix-api-documentation.md
  - name: SessionLogin
    type: http
    scheme: custom
    description: >-
      POST /api/login exchanges loginId + password (+ optional TOTP for MFA) for a
      session; POST /api/logout ends it.
    source: https://docs.trustlogix.io/trustlogix-api-documentation.md
  - name: MCP-OAuth2
    type: oauth2
    flow: authorizationCode
    description: >-
      The TrustAI MCP Server authorizes agent connections with OAuth 2.0,
      implementing RFC 9728 Protected Resource Metadata per the MCP Authentication
      Specification. End-user OAuth tokens are propagated in the Authorization
      header to carry end-user identity to the policy engine.
    standards: [RFC9728]
    source: https://docs.trustlogix.io/trust-ai/mcp-server.md
  - name: SSO-OIDC
    type: openIdConnect
    description: >-
      Console/tenant single sign-on via Azure Active Directory (MS Entra) and Okta,
      with SCIM 2.0 user provisioning/deprovisioning and a regenerable SCIM token.
    identity_providers: [Azure AD / MS Entra, Okta]
    provisioning: SCIM 2.0
    source: https://docs.trustlogix.io/integrations/single-sign-on.md

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/trustlogix-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.