Exec · Authentication Profile

Exec Authentication

Authentication

Exec secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyArtificial IntelligenceSales EnablementTrainingRoleplayCoachingLearningKnowledge-ManagementLMS
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑
generated: '2026-07-19'
method: searched
source: openapi/exec-openapi-original.yml
docs: https://docs.exec.com/api-reference/authentication
summary:
  types:
  - http
  http_schemes:
  - bearer
  api_key_in: []
  oauth2_flows: []
  scopes: none
  access: full-admin
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: |-
    API key created in Settings > API. Passed as `Authorization: Bearer [example key]`.

    Format: `exec_live_` followed by 40 alphanumeric characters.
    Keys grant full admin access to the workspace (no scopes/permissions).
    Keys are shown only once at creation; deactivation is reversible, deletion is permanent.
  key_prefix: exec_live_
  test_prefix: null
  sources:
  - openapi/exec-openapi-original.yml
  docs: https://docs.exec.com/api-reference/authentication
platform_sso:
  scope: workspace sign-in, not API authorization
  availability: Enterprise plan
  provider: WorkOS
  docs: https://docs.exec.com/sso-directory-sync
  protocols:
    - {id: saml-2.0, details: SP-initiated and IdP-initiated SSO flows}
    - {id: oidc, details: OAuth 2.0 authorization code grant with ID tokens}
    - {id: scim-2.0, details: Automated user and group provisioning and deprovisioning}
  identity_providers_tested: [Okta, Microsoft Entra ID, Google Workspace, OneLogin, PingFederate,
    PingOne, JumpCloud, Duo, AD FS, Rippling, CyberArk]
  behavior:
    mandatory_once_enabled: true
    jit_provisioning: false
    note: >-
      SSO alone does not create accounts; users must be invited into Exec unless
      SCIM directory sync is also enabled.
  self_service: Workspace admins configure SSO in Settings > Security without contacting support.
lti_1_3:
  scope: LMS launch identity, not API authorization
  docs: https://docs.exec.com/lti/overview
  endpoints_published: [OIDC login, launch, JWKS, OpenID configuration]
  registration: [dynamic registration, manual connection]
notes: >-
  No test/sandbox key variant is documented (only exec_live_). The REST API has no
  OAuth or scope surface, so scopes/ is intentionally omitted for this provider.
  Enterprise SSO (SAML/OIDC) and SCIM directory sync govern human sign-in and user
  provisioning only — they issue no API credential and grant no API scope.

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/exec-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 email required.

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