Ellipse Gradient for Header

PartnerStack Integration Guide

Connect PartnerStack partner, deal, commission, reward, and transaction data with enterprise systems through REST APIs, selected webhook events, and Martini workflows.

PartnerStack integration options at a glance

PartnerStack’s primary integration mechanism is its REST API, which provides access to partner ecosystem data including Partners, Companies, Deals, Commissions, Rewards, Transactions, and Programs. PartnerStack also supports webhook-style notifications for selected events, enabling near-real-time workflow initiation when coverage is available. For objects or events without notifications, Martini can run scheduled, paginated REST API workflows with bounded extraction windows and persisted watermarks where supported. PartnerStack uses API-key authentication for documented API access. Martini can securely store the key, consume REST responses, receive supported webhook notifications, transform payloads, apply business rules, and deliver normalized data to CRM, finance, reporting, or other enterprise systems.

Integration pointSupported by PartnerStack?Common use casesHow Martini supports it
REST APIsYesRetrieve and manage Partners, Companies, Deals, Commissions, Rewards, Transactions, Programs, and related partner ecosystem data. REST is the primary interface for current PartnerStack integrations.Martini can consume PartnerStack REST endpoints from workflows, handle pagination, map responses, apply business rules, and expose normalized results through Martini APIs.
Webhooks / outbound callbacksLimitedPartnerStack supports webhook-style notifications for selected events, such as partner or deal activity where coverage is available. Event and object coverage should be verified before production use.Martini can expose an inbound webhook endpoint, validate and deduplicate notifications, retrieve the complete resource when needed, and start downstream workflows.
AuthenticationYesPartnerStack documents API-key authentication for API access. The applicable header format, account permissions, and current API requirements should follow PartnerStack’s documentation.Martini can store the API key as a secret and use it in REST API configuration without embedding credentials in workflow logic or source files.
Scheduled synchronizationYesScheduled processing is appropriate for objects or events without webhook coverage and for recurring reconciliation of partners, companies, deals, commissions, rewards, and transactions.Martini can schedule workflows, retrieve paginated lists, persist watermarks where supported, throttle requests, and resume processing after transient failures.
Pagination and incremental retrievalYesPartnerStack list endpoints should be processed with documented pagination parameters. Updated-at filtering or another reliable watermark can be used where the endpoint supports it.Martini can iterate through pages, bound extraction windows, persist checkpoints, and perform idempotent upserts into target systems.
Bulk / asynchronous APIsNot confirmedA dedicated PartnerStack bulk or asynchronous API was not confirmed. Large transfers should use documented REST list endpoints and controlled scheduling.Martini can orchestrate paginated REST requests and batch processing, but the workflow should not assume a PartnerStack bulk API.
GraphQL APIsNot confirmedNo official public PartnerStack GraphQL API documentation was confirmed. REST should be treated as the primary integration interface.Martini can consume GraphQL APIs generally, but PartnerStack integrations should use REST unless a supported GraphQL endpoint is separately confirmed.
SOAP APIsNot confirmedNo official public PartnerStack SOAP API documentation was confirmed.Martini supports SOAP consumption generally, but a PartnerStack SOAP integration should not be assumed.

How PartnerStack exposes data and business events

PartnerStack REST APIs

PartnerStack provides REST API access for retrieving and managing partner ecosystem data, including Partners, Companies, Deals, Commissions, Rewards, Transactions, and Programs. REST is the primary documented mechanism and is suitable for both targeted API requests and scheduled synchronization.

Martini implementation pattern

Martini implementation pattern: Martini stores the PartnerStack API key as a secret, invokes the relevant REST endpoint, handles pagination and response validation, maps the returned object into a canonical model, applies business rules, and writes the result to the target system. For large or recurring transfers, the workflow persists checkpoints and uses idempotent upserts.

Implementation sequence

Authenticate the request with the PartnerStack API key
Invoke the documented PartnerStack REST endpoint
Process response pages within a bounded extraction window
Validate required fields and object relationships
Map the PartnerStack object to the target data model
Apply status, ownership, settlement, or eligibility rules

PartnerStack webhook-style notifications

PartnerStack supports webhook-style notifications for selected events. Coverage is event-specific rather than universal, so integrations should verify whether the required object and lifecycle event are available and use REST polling for gaps.

Martini implementation pattern

Martini implementation pattern: Martini exposes an inbound endpoint for supported PartnerStack notifications, applies the currently documented verification requirements, records an event identifier or hash, and retrieves the current PartnerStack resource when the notification is incomplete. The workflow then maps and routes the event to downstream systems while handling retries and out-of-order delivery.

Implementation sequence

Receive the PartnerStack webhook notification
Verify the request according to current PartnerStack requirements
Check the event identifier or hash for duplicate delivery
Retrieve the current PartnerStack resource when necessary
Validate and map the event to the target model
Apply downstream business rules and record the processing outcome

Common PartnerStack integration patterns

Pattern 1: Synchronize partners and companies to a CRM

When to use this pattern

Use this pattern when Salesforce, HubSpot, or another customer-facing system needs current PartnerStack partner and company data. Scheduled retrieval is appropriate when webhook coverage is unavailable or when a regular reconciliation process is required.

Integration direction
PartnerStack
Martini
Salesforce
Example Mapping
PartnerStack FieldCanonical FieldTarget Field
PartnerStack Partner IDpartnerExternalIdPartner External ID
Partner namepartnerNameAccount Name
Company IDcompanyExternalIdAccount External ID
Company namecompanyNameAccount Name
Martini implementation pattern

A scheduled Martini workflow retrieves paginated Partners and Companies, optionally limits extraction by a supported modification timestamp, and resolves relationships using stable identifiers. It validates required fields, applies matching and ownership rules, performs idempotent upserts, and sends missing references or validation failures to an exception path rather than creating ambiguous records.

Martini capabilities used
  • workflows
  • scheduling
  • API consumption
  • pagination orchestration
  • data mapping
  • business rules
  • error handling

Pattern 2: Synchronize partner-referred deals to sales operations

When to use this pattern

Use this pattern when PartnerStack deal activity must update a CRM or when a CRM opportunity must be reflected in PartnerStack. Selected PartnerStack webhook events can provide near-real-time initiation, while REST retrieval supports complete-resource synchronization.

Integration direction
PartnerStack
Martini
Salesforce
Example Mapping
PartnerStack FieldCanonical FieldTarget Field
Deal IDdealExternalIdOpportunity External ID
Company IDcompanyExternalIdAccount External ID
Deal statusdealStatusOpportunity Stage
Partner IDpartnerExternalIdPartner Attribution ID
Martini implementation pattern

Martini receives a supported notification or retrieves changed Deals on a schedule, then fetches the current Deal when the event contains only a reference. The workflow maps status, company, partner, and value fields, applies rules for valid lifecycle transitions, upserts the opportunity, and retries transient failures while preserving the PartnerStack identifier for reconciliation.

Martini capabilities used
  • webhooks
  • API consumption
  • workflow orchestration
  • data mapping
  • business rules
  • idempotency
  • retry handling

Pattern 3: Export commissions and rewards to finance

When to use this pattern

Use this pattern when finance, ERP, payroll, or reporting systems require approved PartnerStack Commissions, Rewards, and related Transactions. It is suited to scheduled settlement-period processing and reconciliation.

Integration direction
PartnerStack
Martini
Stripe
Example Mapping
PartnerStack FieldCanonical FieldTarget Field
Commission IDcommissionExternalIdExternal Commission ID
Reward statussettlementStatusPayout Status
Transaction amounttransactionAmountSettlement Amount
Partner IDpartnerExternalIdPayee Partner ID
Martini implementation pattern

A scheduled workflow retrieves Commissions, Rewards, and Transactions using status and period filters, validates partner and company references, and transforms amounts and statuses into the destination model. Martini uses deterministic keys to prevent duplicate exports, records counts and totals, and routes mismatches or failed reconciliation to an exception workflow.

Martini capabilities used
  • scheduling
  • API consumption
  • data mapping
  • financial business rules
  • idempotent processing
  • reconciliation
  • error handling

Pattern 4: Publish a normalized partner activity data service

When to use this pattern

Use this pattern when multiple internal consumers need consistent PartnerStack data for reporting, partner operations, or downstream applications. It reduces repeated vendor-specific API logic by centralizing retrieval and normalization.

Integration direction
PartnerStack
Martini
Salesforce
Example Mapping
PartnerStack FieldCanonical FieldTarget Field
Program IDprogramExternalIdPartner Program ID
Deal statusdealStatusSales Pipeline Status
Commission amountcommissionAmountAttributed Commission
Transaction dateactivityDatePartner Activity Date
Martini implementation pattern

Martini retrieves and normalizes PartnerStack objects through reusable workflows, applies filtering and relationship resolution, and exposes the approved model through a Martini API or writes it to a reporting destination. The implementation isolates PartnerStack mappings, logs source identifiers, and uses checkpointing and retry handling for dependable refreshes.

Martini capabilities used
  • workflows
  • API consumption
  • API exposure
  • data transformation
  • reusable integration assets
  • business rules
  • monitoring

Applications commonly integrated with PartnerStack

PartnerStack data can be coordinated with sales, billing, marketing, collaboration, and analytics applications. The exact objects and direction should be confirmed against each application’s current API and the PartnerStack account configuration; Martini can orchestrate these exchanges without requiring a dedicated PartnerStack connector.

Application Scenario Direction Martini Pattern
Salesforce Synchronize partner-referred deals, companies, contacts, opportunity status, and revenue attribution between partner operations and sales processes. PartnerStack → Martini → Salesforce Use PartnerStack webhooks for selected deal events and scheduled REST synchronization for Partners and Companies. Retrieve complete objects, map stable PartnerStack identifiers to Salesforce fields, apply ownership and status rules, and upsert records with retry and exception handling.
HubSpot Connect partner referrals and deal activity with marketing and sales pipelines while preserving partner attribution. PartnerStack → Martini → HubSpot Consume selected PartnerStack notifications or poll paginated REST endpoints, normalize Companies and Deals, match by stable identifiers, and use conditional upserts to prevent duplicate companies or deals. Route unmapped partner references to an exception workflow.
Stripe Reconcile customer or subscription activity with partner attribution, commissions, and rewards. Stripe → Martini → PartnerStack Receive or retrieve Stripe billing activity through an API workflow, apply partner and settlement-period rules, and call PartnerStack REST endpoints where the required account permissions and endpoints are available. Persist correlation identifiers and reconcile downstream statuses.
Slack Notify sales, partner, finance, and operations teams about referrals, deal approvals, commission exceptions, or reward and payout events. PartnerStack → Martini → Slack Trigger Martini from supported PartnerStack events or scheduled status checks, evaluate notification rules, format a concise message with the PartnerStack identifier and status, and send only actionable exceptions or milestones to designated Slack channels.
Zapier Connect PartnerStack events or data with smaller operational applications and internal workflows where selected triggers or actions are appropriate. PartnerStack → Martini → Zapier Use Martini as the controlled orchestration layer for selected PartnerStack REST calls and webhook events, normalize payloads, validate required fields, and exchange only approved data with Zapier endpoints while recording event and request identifiers.
Segment Combine partner attribution with product, account, and customer lifecycle events for reporting and activation use cases. Segment → Martini → PartnerStack Receive relevant product or customer activity through an API endpoint or scheduled retrieval process, resolve the PartnerStack Company or Partner identifier, apply eligibility rules, and publish or write the resulting attribution data to the required destination.
Marketo Associate partner-originated activity with marketing campaigns, leads, and revenue attribution. PartnerStack → Martini → Marketo Retrieve or receive PartnerStack partner and deal activity, map identifiers and campaign attributes to Marketo’s model, apply consent and deduplication rules, and send validated updates with retry handling and reconciliation reporting.

How to build a PartnerStack integration in Martini

Objective

Establish PartnerStack API access without placing credentials in workflow logic or source files.

Instructions in Martini

  • Configure PartnerStack REST requests with the documented API-key authentication format
  • Store the API key in Martini secrets management
  • Confirm the account permissions and API version needed for the selected objects
  • Define target-system credentials and environment-specific configuration

Objective

Select an event-driven or scheduled initiation method based on PartnerStack coverage and synchronization requirements.

Instructions in Martini

  • Use a Martini inbound endpoint for supported PartnerStack webhook-style notifications
  • Use a scheduler trigger for objects or events without confirmed webhook coverage
  • Define extraction windows and checkpoint behavior for recurring synchronization
  • Set bounded concurrency and throttling appropriate to the PartnerStack plan

Objective

Obtain complete, current PartnerStack objects and process collection endpoints reliably.

Instructions in Martini

  • Invoke the documented REST endpoint for Partners, Companies, Deals, Commissions, Rewards, Transactions, or Programs
  • Process list responses using PartnerStack pagination parameters
  • Retrieve the full resource when a webhook contains only an identifier
  • Persist a watermark or last successful page where the endpoint supports incremental retrieval

Objective

Coordinate validation, enrichment, routing, and target-system operations in a maintainable Martini workflow.

Instructions in Martini

  • Create a workflow for the selected synchronization or event process
  • Separate transient API failures from validation, authentication, and business-rule failures
  • Resolve related PartnerStack identifiers before writing dependent objects
  • Route exceptions to a review or replay process

Objective

Convert PartnerStack payloads into a canonical model and the target application’s schema.

Instructions in Martini

  • Map stable PartnerStack identifiers to external-ID fields
  • Transform statuses, dates, amounts, and relationships into target formats
  • Validate required fields and known lifecycle values
  • Keep vendor-specific mappings isolated from downstream business rules

Objective

Ensure only eligible, correctly matched, and appropriately timed data is propagated.

Instructions in Martini

  • Apply partner, company, deal, commission, reward, and settlement-period rules
  • Use upsert logic and deterministic keys to prevent duplicates
  • Handle missing references and ambiguous matches explicitly
  • Reconcile counts and financial totals before marking a batch complete

Common PartnerStack data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
PartnersRepresent organizations or individuals participating in a PartnerStack program and support partner identity, status, and attribution workflows.Salesforce, HubSpot, Marketo, reporting databasesMartini retrieves Partners through paginated REST workflows, matches stable PartnerStack identifiers, maps fields to the target model, and performs idempotent create or update operations.
CompaniesRepresent customer or prospect companies associated with partner activity, referrals, and deal relationships.Salesforce, HubSpot, Segment, data warehousesMartini resolves company identifiers and relationships, validates required fields, applies matching rules, and routes missing or ambiguous mappings to an exception process.
DealsRepresent partner-referred or partner-influenced business opportunities and their lifecycle status.Salesforce, HubSpot, reporting and revenue systemsMartini can receive selected event notifications or poll REST endpoints, retrieve the current Deal, map attribution and status fields, and upsert the target opportunity with retry protection.
CommissionsRepresent commission records generated from eligible partner activity and their approval or settlement state.Accounting systems, ERP platforms, payroll systems, data warehousesMartini retrieves Commissions with status and settlement-period filters, validates partner and transaction references, applies financial rules, and exports approved data with reconciliation controls.
RewardsRepresent partner rewards or payouts associated with program activity.Accounting systems, ERP platforms, payroll systems, reporting platformsMartini processes Rewards as changing lifecycle objects rather than one-time inserts, uses deterministic identifiers, and records export outcomes for reconciliation.
TransactionsRepresent financial or activity transactions used to calculate commissions and rewards.Finance platforms, ERP systems, reporting databases, data warehousesMartini retrieves Transactions in bounded windows, transforms amounts and statuses, correlates them with Partners, Companies, Deals, or Commissions, and prevents duplicate processing.

Authentication and security considerations

API-key authentication

PartnerStack documents API-key authentication for general API access. Store the key in Martini secrets management and supply it through the configured request rather than embedding it in workflow logic or source files.

Permissions and webhook verification

Access depends on the PartnerStack account, API key, and available permissions. Exact permission requirements should be verified for the selected objects. PartnerStack webhook signing or secret-header requirements were not conclusively confirmed, so inbound workflows should implement the currently documented verification mechanism before production use.

Transport and data protection

  • Restrict API credentials to the minimum account permissions required.
  • Keep secrets separate across development, test, and production environments.
  • Redact API keys and sensitive financial data from logs.
  • Validate inbound event payloads and prevent replay or duplicate processing.

Operational considerations for PartnerStack integrations

Pagination and rate limits

Use documented pagination parameters and bounded extraction windows. Confirm rate limits for the PartnerStack plan and API version, then apply throttling, bounded concurrency, retry delays, and response-aware handling for HTTP 429 responses.

Lifecycle and idempotency

Deals, Commissions, Rewards, and Transactions can change after creation. Synchronization should support updates and reconciliation, use stable PartnerStack identifiers, and record event identifiers or deterministic keys to prevent duplicate processing.

Schema and matching

Isolate PartnerStack mappings, validate required fields and status values, and monitor for API version or schema changes. Define system ownership for partner, company, deal, and financial data, and do not rely on names or email addresses alone for matching.

Testing and operations

Test webhook replay, pagination boundaries, rate-limit responses, missing references, status transitions, and financial reconciliation. Monitor workflow logs and separate transient failures from malformed payloads, permission problems, and business-rule exceptions.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration beyond a script

Martini provides a maintainable workflow layer for PartnerStack API calls, webhook intake, scheduled synchronization, pagination, validation, transformation, target-system writes, and exception routing. This keeps integration behavior visible and reusable as requirements evolve.

Controlled data movement

Instead of coupling PartnerStack directly to each application, Martini can normalize Partners, Companies, Deals, Commissions, Rewards, and Transactions and apply consistent business rules before distributing data to CRM, finance, reporting, or collaboration systems.

Reliability and reuse

  • Use secrets and environment-specific configuration for secure deployment.
  • Apply idempotent upserts, checkpoints, throttling, and retry policies.
  • Expose normalized data through Martini APIs when multiple consumers need a common contract.
  • Centralize monitoring, error handling, and reconciliation rather than duplicating logic across point-to-point scripts.

Frequently asked questions

How can PartnerStack be integrated with enterprise systems?

PartnerStack can be integrated primarily through its REST APIs, which provide access to Partners, Companies, Deals, Commissions, Rewards, Transactions, Programs, and related data. PartnerStack also supports webhook-style notifications for selected events. Systems without notification coverage can use scheduled, paginated REST synchronization with API-key authentication.

Can Martini integrate with PartnerStack?

Yes. Martini can consume PartnerStack REST APIs, receive supported PartnerStack webhook-style notifications through an inbound endpoint, schedule synchronization workflows, map and transform PartnerStack objects, and deliver the results to CRM, finance, reporting, or other enterprise systems.

Do I need a connector to integrate PartnerStack with Martini?

No. A dedicated PartnerStack connector is not required. Martini can integrate using PartnerStack’s confirmed native mechanisms, primarily its REST APIs, selected webhook-style notifications, and API-key authentication.

Is there any extra Lonti cost to integrate PartnerStack with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate PartnerStack. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from PartnerStack, cloud infrastructure, or other third-party systems depending on subscription, usage, and deployment model.

Which PartnerStack integration methods should be used?

REST APIs should be the primary method for current PartnerStack integrations. Use webhook-style notifications for selected events when the required coverage is confirmed, and scheduled REST polling for objects or events without notifications. A public GraphQL API, SOAP API, and dedicated bulk API were not confirmed.

Are PartnerStack events or webhooks available?

PartnerStack supports webhook-style notifications for selected events, but coverage is event- and object-specific rather than universal. Martini can receive supported notifications, validate them according to the current PartnerStack requirements, deduplicate them, and retrieve the current resource when necessary. Scheduled polling should cover notification gaps.

How does synchronization and data mapping work?

Martini workflows can retrieve or receive PartnerStack objects, process pagination, map fields into a canonical model, apply status and ownership rules, and upsert data into target systems. Stable PartnerStack identifiers should be retained for matching and reconciliation, while watermarks and bounded extraction windows support recurring synchronization.

How are PartnerStack errors, retries, and duplicates handled?

Martini can distinguish transient HTTP failures, rate-limit responses, authentication issues, malformed payloads, missing references, and business-rule failures. Transient failures can be retried with delay, while event identifiers, object identifiers, deterministic keys, and persisted checkpoints help prevent duplicate processing. Exceptions can be routed for review or replay.

Related Martini documentation

APIs

Workflows

Mapping

Security

Connect PartnerStack with your enterprise systems

Use Martini to orchestrate secure PartnerStack API and webhook integrations, synchronize partner ecosystem data, and deliver reliable workflows across CRM, finance, reporting, and operational applications.

EXPLORE MARTINI
BOOK A DEMO