PartnerStack

PartnerStack

PartnerStack is partner-program operations first: enumerate groups and partnerships, then customers, deals, leads, transactions, and rewards. Vendor API v2 uses Basic auth (public key + secret key) and cursor pagination via starting_after / ending_before.

Operational order

1. get groups — resolve group_key before inviting or moving partners.
2. get partnerships — find partner_key and claim status.
3. get customers — attributed accounts; use key from list rows for single fetch.
4. get deals / get leads — pipeline objects; stages must match group settings.
5. get transactions — revenue events that drive rewards; min_created filters large histories.
6. get rewards — list-only payout audit (no single-key GET upstream).

Data model

• Groups — segment partners (campaigns, assets, rewards). List-only API.
• Partnerships — partner accounts; archive via delete, not hard purge.
• Customers — referred signups; prefer Server-to-Server for click attribution over manual create.
• Deals — registered opportunities with stage and amount in cents.
• Leads — inbound leads routed to partners.
• Transactions — billable events; exactly one of customer_key, customer_email, or customer_external_key on create.
• Rewards — issued incentives; create-only manual grants.

Gotchas

• Pagination — default page size is small; pass limit up to 100 and follow data.has_more with starting_after set to the last item key.
• Amounts — deal_amount, transaction amount, and reward amount are in cents.
• Test keys — customers and transactions created with test credentials stay sandbox; use partner_key gstest for test flows.
• Groups and rewards reads — no single-row GET; always list and filter client-side or with min_created.
• Partnership key — pass key from a list row; invented keys return 404 (not a platform bug).