Impartner · Authentication Profile

Impartner Authentication

Authentication

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

CompanySoftware-as-a-ServicePartner Relationship ManagementPRMChannel ManagementPartner EcosystemThrough-Channel MarketingSalesCRM
Methods: oauth2, openIdConnect, apiKey Schemes: 3 OAuth flows: authorizationCode, clientCredentials, password, deviceCode API key in: header

Security Schemes

OpenIDConnect openIdConnect
OAuth2 oauth2
· flows: authorizationCode, clientCredentials
ApiKey apiKey
· in: header ()

Source

Authentication Profile

impartner-authentication.yml Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://login.impartner.com/.well-known/openid-configuration
docs: https://developer.impartner.com
summary:
  types: [oauth2, openIdConnect, apiKey]
  oauth2_flows: [authorizationCode, clientCredentials, password, deviceCode]
  api_key_in: [header]
  identity_provider: Auth0 (tenant impartner.auth0.com, public issuer https://login.impartner.com/)
schemes:
- name: OpenIDConnect
  type: openIdConnect
  openIdConnectUrl: https://login.impartner.com/.well-known/openid-configuration
  issuer: https://login.impartner.com/
  authorization_endpoint: https://login.impartner.com/authorize
  token_endpoint: https://login.impartner.com/oauth/token
  userinfo_endpoint: https://login.impartner.com/userinfo
  jwks_uri: https://login.impartner.com/.well-known/jwks.json
  revocation_endpoint: https://login.impartner.com/oauth/revoke
  device_authorization_endpoint: https://login.impartner.com/oauth/device/code
  token_endpoint_auth_methods: [client_secret_basic, client_secret_post, private_key_jwt, none]
  code_challenge_methods: [S256, plain]
  sources: [well-known/impartner-openid-configuration.json]
- name: OAuth2
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://login.impartner.com/authorize
    tokenUrl: https://login.impartner.com/oauth/token
  - flow: clientCredentials
    tokenUrl: https://login.impartner.com/oauth/token
  sources: [well-known/impartner-openid-configuration.json]
- name: ApiKey
  type: apiKey
  in: header
  note: >-
    The Impartner Objects API (v1, base https://prod.impartner.live) is also accessed with an API
    key issued per-tenant; per Impartner integration docs the key is obtained by contacting an
    Impartner representative. Third-party connectors (Cortex XSOAR, Tray) authenticate with this key.
  sources: [https://xsoar.pan.dev/docs/reference/integrations/impartner]
notes:
- The platform SSO / app login is OAuth2 + OIDC on an Auth0 tenant (login.impartner.com).
- The programmatic Objects API uses a tenant API key; SOAP and REST are both offered.

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

GitHub Google LinkedIn

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