01 · Records and state owned
Programs, groups and segments, partners, customers, leads and deals, transactions, offers, rewards and commissions, links, and webhook events.
PartnerStack
PartnerStack
A leading B2B partner platform for programs, partners, referrals, deals, rewards, and payouts with a developer API suitable for customer-owned partner operations interfaces.
Partnerships & ecosystemSystem of recordExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Read vendor-side partner-program records and partner-side marketplace programs, partnerships, customers, payouts, rewards and transactions, with webhooks or postbacks for supported events.
03 · Actions and write paths
Create, update or archive supported partner, customer, lead, deal, partnership, transaction and program records; manage webhooks; and create rewards through authorized vendor operations.
04 · Authentication and permissions
Vendor API requests use Basic Auth with public and private keys and separate Test and Production credentials. Partner API requests use a user API key as a bearer token, so vendor and partner contexts must not be conflated.
05 · Monitoring, approval, and recovery
Preserve partner, customer and attribution identifiers; keep Test and Production records separate; and require financial review before transaction or reward creation, attribution changes, or any action that can affect commissions and payouts.
06 · Limits and caveats
Vendor Test and Production keys are separate with no mode toggle, and test transactions can be added only to test customers. Partner API list operations use cursor pagination, and available writes depend on the authorized vendor context.
First-party access
Documented surfaces
Agent access
MCP support
Third-party onlyThird-party/community MCP only
Support: Third-party only
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Not applicable to a first-party MCP provider.
Approval boundary: Require confirmation before creating or deleting customers, leads, deals, partnerships or transactions and require financial approval before creating rewards or changing attribution-bearing records.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access1
Identity4
Governance4
Agent access1
UI extensibility4
Portability3
Observability3
Documentation2
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that PartnerStack ships them.
Single-platform patterns
- B2B partner pipeline and enablement cockpit
- Partner ecosystem cockpit
- Referral and attribution debugger
- Partner onboarding workspace
Multi-platform compositions
- PartnerStack + CRM or commerce system: partner ecosystem cockpit
- PartnerStack + payments or finance platform + content or learning system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
3 recorded sources
Platform core validationRepresentative source
https://docs.partnerstack.com/docs/partnerstack-api ↗Programs, groups and segments, partners, customers, leads and deals, transactions, offers, rewards and commissions, links, and webhook events. Create or update supported partners, customers, leads/deals, transactions,…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party core-access review
Developer docsSource inventory
https://docs.partnerstack.com/ ↗First-party API documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://partnerstack.com/ ↗Product overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.