Impartner

Impartner is a SaaS-based Partner Relationship Management (PRM) and partner revenue orchestration platform, founded in 1997 and headquartered in South Jordan, Utah, and backed by Emergence Capital. It helps enterprises manage the full indirect-channel lifecycle - partner recruitment, onboarding, deal registration, co-selling, through-channel marketing automation (TCMA), and performance measurement - from a single connected system. For developers and integrators, Impartner exposes an Objects API (version 1) over both REST and SOAP, queried with THQL (The Impartner Query Language), secured by an Auth0-based OAuth2 / OpenID Connect identity layer plus per-tenant API keys, and extended through workflow-engine webhooks and a family of first-party @impartner npm packages, design system, and CLI for building applications on Impartner Orchestration Studio.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

How we profile Impartner

Each block below is one kind of artifact we hold for Impartner. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 1

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Impartner Objects API

REST and SOAP object API (v1) for reading and writing Impartner platform records (accounts, partners, deals, and tenant-defined custom objects) using the THQL query language wit...

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

impartner-mcp.yml

MCP SERVER

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Impartner Webhooks

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Impartner Authentication

oauth2/openIdConnect/apiKey · 3 schemes

SECURITY

Impartner Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Impartner Scopes

14 scopes

14 scopes

SCOPES

Resources

Every other property we hold for Impartner — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

← All providers · Data indexed from github.com/api-evangelist/impartner · machine-readable index on apis.io