generated: '2026-09-05'
method: searched
source: https://docs.ixhello.com/ixhc2/integrations/outbound-calling-api-user-guide
docs: https://docs.ixhello.com/ixhc2/integrations/outbound-calling-api-user-guide
note: >-
  Concentrix publishes no OpenAPI, so this profile is read from the iX Hello Customer v2
  documentation rather than derived from securitySchemes. Two distinct auth surfaces exist:
  (1) organization-scoped API keys presented as a bearer token on the public iX Hello Customer v2
  APIs, and (2) Azure AD B2C OpenID Connect for interactive sign-in to the iX Hello application.
summary:
  types: [http, openIdConnect]
  api_key_in: [header]
  oauth2_flows: [authorizationCode, implicit]
schemes:
  - name: ixHelloApiKey
    type: http
    scheme: bearer
    in: header
    parameter: Authorization
    description: >-
      "Authorization: Bearer <api_key>". API keys are provisioned per organization, stored in the
      platform's Secrets Manager, and shared between the Headless Flow Execution API and the
      Outbound Calling API. The platform validates the orgId in every request path against the key;
      a key cannot reach flows or call records belonging to another organization.
    applies_to:
      - iX Hello Customer v2 Universal Messaging API (headless flow execution)
      - iX Hello Customer v2 Outbound Calling API
    provisioning: contact the iX Hello product team — no self-service key issuance is documented
    sources:
      - https://docs.ixhello.com/ixhc2/integrations/outbound-calling-api-user-guide
      - https://docs.ixhello.com/ixhc2/integrations/executing-flow-via-api-headless-execution
    errors:
      - {status: 401, code: AUTH_HEADER_MISSING, meaning: Authorization header was not provided}
      - {status: 401, code: INVALID_TOKEN, meaning: API key is invalid, revoked, or expired}
      - {status: 403, code: PERMISSION_DENIED, meaning: org lacks the outbound_calling permission, or the flow belongs to a different org}
  - name: ixPlatformB2C
    type: openIdConnect
    openIdConnectUrl: https://ixadminprodk5.b2clogin.com/2c95ae7b-5bab-49e0-a483-62a3cd3867ba/b2c_1a_signup_signin/v2.0/.well-known/openid-configuration
    description: >-
      Azure AD B2C tenant fronting interactive sign-in to the iX Hello application
      (www.ixhello.com). Discovery document fetched anonymously and saved verbatim to
      well-known/concentrix-openid-configuration.json.
    issuer: https://ixadminprodk5.b2clogin.com/tfp/2c95ae7b-5bab-49e0-a483-62a3cd3867ba/b2c_1a_signup_signin/v2.0/
    authorization_endpoint: https://ixadminprodk5.b2clogin.com/2c95ae7b-5bab-49e0-a483-62a3cd3867ba/b2c_1a_signup_signin/oauth2/v2.0/authorize
    token_endpoint: https://ixadminprodk5.b2clogin.com/2c95ae7b-5bab-49e0-a483-62a3cd3867ba/b2c_1a_signup_signin/oauth2/v2.0/token
    jwks_uri: https://ixadminprodk5.b2clogin.com/2c95ae7b-5bab-49e0-a483-62a3cd3867ba/b2c_1a_signup_signin/discovery/v2.0/keys
    scopes_supported: [openid]
    id_token_signing_alg_values_supported: [RS256]
    claims_supported: [sub, tid, name, email, orgId, orgName, zoneinfo, locale, citizenOf, given_name, family_name, iss, iat, exp, aud, acr, nonce, auth_time]
    sources:
      - well-known/concentrix-openid-configuration.json
webhook_authentication:
  mechanism: HMAC-SHA256 payload signature
  header: X-Signature
  format: sha256=<hex>
  secret: caller-supplied "webhookAuth" value from the call-initiation request
  computation: HMAC-SHA256(webhookAuth, rawRequestBody)
  note: >-
    webhookAuth is NOT forwarded as an Authorization header — it only signs the payload. If it is
    omitted the callback is still sent, signed with an empty secret (effectively unsigned).
  source: https://docs.ixhello.com/ixhc2/integrations/outbound-calling-api-user-guide