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.
Impartner publishes 1 API on the APIs.io network. Tagged areas include Company, SaaS, Partner Relationship Management, PRM, and Channel Management.
The Impartner catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Impartner’s developer surface includes documentation, API reference, pricing, engineering blog, support, authentication, CLI, and 16 more developer resources.
Kin Score
APIs 1
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 that expose these APIs to AI agents.
impartner-mcp.yml
MCP SERVEREvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Impartner Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API