Integration

PartnerStack integration

PartnerStack runs partner, affiliate and reseller programs. With the Vendor API you can manage partnerships, partner applications and partner teams, record customers, transactions, actions, leads and deals so partners earn rewards, create and list rewards, manage products, product books, tiers and groups, read form templates and sales-cycle stages, export custom reports and base records, and manage webhooks. Deal file downloads are not exposed (the route only returns a file URL), and the separate Partner API and S2S conversion tracking API are not part of this integration. Authentication is HTTP Basic with the vendor public key as username and secret key as password (Settings, Integrations, PartnerStack API Keys); test keys create test records.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in PartnerStack.Built from the 75 PartnerStack tools below, on the connection you add once.

What you can do with PartnerStack

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Deal, 7 operations

  • archive_dealArchive dealDELETEArchives a deal.
  • assign_deal_partnershipAssign deal partnershipPOSTAssigns a deal to a partnership and the partner team member identified by stack_key, so that partner owns the deal.
  • convert_dealConvert dealPOSTConverts a deal into a customer with the given email (and customer_key, else the email is used as the key). The new customer can then earn the partner rewards.
  • create_dealCreate dealPOSTCreates a deal for a partner (source partner) or a group (source vendor). account_name, amount in cents, close_date, contact names and a stage from list_sales_cycle_stages are required.
  • get_dealGet dealGETRetrieves the details of an existing deal. You need only supply the unique deal key that was returned upon deal creation.
  • list_dealsList dealsGETReturns a list of your deals. The deals are returned sorted by creation date, with the most recent deals appearing first.
  • update_dealUpdate dealPATCHUpdates a deal; only the fields sent change. Leave a field out to keep its current value.

Lead, 6 operations

  • archive_leadArchive leadDELETEArchives a lead.
  • convert_leadConvert leadPOSTConverts a lead into a customer (customer_key and email default to the lead's external_key). The new customer can then earn the partner rewards.
  • create_leadCreate leadPOSTCreates a lead submitted by a partner. external_key (unique) and meta with the contact's first and last name are required; list_lead_form_templates shows the other fields.
  • get_leadGet leadGETRetrieves the details of an existing lead. You need only supply the unique lead key that was returned upon lead creation.
  • list_leadsList leadsGETReturns a list of your leads. The leads are returned sorted by creation date, with the most recent leads appearing first.
  • update_leadUpdate leadPATCHUpdates a lead; only the fields sent change. Leave a field out to keep its current value.

Partnership, 6 operations

  • archive_partnershipArchive partnershipDELETEArchives a partnership (the partner leaves the program). delete_links true also deletes the partner's links.
  • create_partnershipCreate partnershipPOSTCreates a partnership (invites a partner to the program). With notify_by_email true PartnerStack emails the partner a verification email; claimed stays false until the partner accepts.
  • get_partnershipGet partnershipGETGets one partnership by partner_key, partnership_key or email: partner name, email, group, tier, manager, status and custom fields.
  • list_partnershipsList partnershipsGETLists partnerships in your program, newest first, filterable by group, email, approval status and dates. Page with starting_after (an item key) while data.has_more is true.
  • move_partnerships_to_groupMove partnerships to groupPATCHMoves several partnerships to another group, given by group_slug or group_id.
  • update_partnershipUpdate partnershipPATCHUpdates a partnership's group, tier, manager, partner_key or custom fields; only the fields sent change.

Customer, 5 operations

  • create_customerCreate customerPOSTCreates a customer attributed to a partner. It cannot link the signup to a referral link or click; for link attribution PartnerStack recommends PartnerStackJS or S2S tracking.
  • delete_customerDelete customerDELETEDeletes (archives) a customer.
  • get_customerGet customerGETGets one customer: email, name, partner, provider key, custom field data and the team member it is assigned to.
  • list_customersList customersGETLists customers referred by partners, newest first, filterable by partner, group, key and dates. Page with starting_after (an item key) while data.has_more is true.
  • update_customerUpdate customerPATCHUpdates a customer's email, name, provider key, responsible member, custom fields or external key. Only the fields sent change.

Product, 5 operations

  • create_productCreate productPOSTCreates a new Product for a customer, based on the given product_book key, customer key, and status.
  • delete_productDelete productDELETEDeletes an existing Product, based on the given unique identifier as either an external key or internal key.
  • get_productGet productGETRetrieves the details of an existing Product, based on the given unique identifier as either an external key or internal key.
  • list_productsList productsGETRetrieves the paginated list of products, optionally filtered by customer key, stack key, or click xid.
  • update_productUpdate productPATCHUpdates the details of an existing Product, based on the given unique identifier as either an external key or internal key.

Product book, 5 operations

  • create_product_bookCreate product bookPOSTCreates a new product book for the company.
  • delete_product_bookDelete product bookDELETEDeletes an existing product book by key
  • get_product_bookGet product bookGETRetrieves the details of an existing product book.
  • list_product_booksList product booksGETRetrieves all product books for the authenticated company. Able to search by keywords in name or description.
  • update_product_bookUpdate product bookPATCHUpdates the specified product book by setting the values of the parameters passed. Any parameters not provided will be left unchanged.

Webhook, 5 operations

  • archive_webhookArchive webhookDELETEArchives a webhook; its events are no longer delivered.
  • create_webhookCreate webhookPOSTRegisters a webhook: PartnerStack POSTs a JSON payload to target_url (any HTTP POST endpoint) for each listed event, such as deal.created. No delivery signature is documented, so deliveries cannot be verified.
  • get_webhookGet webhookGETGets a webhook's events and timestamps (the target URL is not returned).
  • list_webhooksList webhooksGETReturns a list of your webhooks. The webhooks are returned sorted by creation date, with the most recent webhooks appearing first.
  • update_webhookUpdate webhookPATCHChanges a webhook's events or target_url; leave a field out to keep it. PartnerStack documents no delivery signature, so deliveries cannot be verified; the endpoint must accept HTTP POST with a JSON body.

Application, 4 operations

  • create_applicationCreate applicationPOSTSubmits a partner application to a group (program). meta must hold the applicant's first and last name, email and business name; list_form_templates shows the other fields.
  • decide_applicationDecide applicationPATCHApproves or declines one partner application (approved true or false, null clears the decision), optionally moving the partner to a group and assigning a manager and tags.
  • decide_applicationsDecide applicationsPATCHApproves or declines several partner applications at once (approved true or false, null clears the decision), optionally moving them to a group and assigning a manager and tags.
  • list_applicationsList applicationsGETLists partner applications, newest first, filterable by status, email and group. Page with starting_after (an item key) while data.has_more is true.

Tier, 4 operations

  • create_tierCreate tierPOSTCreates a new tier for the given tier collection
  • get_tierGet tierGETRetrieves the details of an existing Tier.
  • list_tiersList tiersGETReturns a list of all tiers.
  • update_tierUpdate tierPATCHUpdates an existing tier with the data provided. Any parameters not passed will not be updated.

Action, 3 operations

  • archive_actionArchive actionDELETEArchives an action. Any rewards or drip rewards attached to it are archived too.
  • create_actionCreate actionPOSTRecords that a partner or customer performed an action (for example a signup step) a number of times. Actions can trigger rewards configured in the program.
  • list_actionsList actionsGETReturns a list of your actions. The actions are returned sorted by creation date by default, with the most recent actions appearing first.

Collection, 3 operations

  • create_tier_collectionCreate tier collectionPOSTCreate a tier collection for a company
  • get_tier_collectionGet tier collectionGETGet a tier collection by key
  • list_tier_collectionsList tier collectionsGETGet all tier collections for a company

Custom report, 3 operations

  • export_custom_reportExport custom reportPOSTExports a saved custom report and emails it to member_email (or posts it to webhook_target_url). Each report can be exported once every 2 hours; each teammate email 20 times every 2 hours.
  • get_custom_reportGet custom reportGETGets one saved custom report's configuration (not its data). Export it with export_custom_report.
  • list_custom_reportsList custom reportsGETLists the custom reports saved in the Performance tab (their configuration, not their data). Export one with export_custom_report.

Form template, 3 operations

  • list_deal_form_templatesList deal form templatesGETFetches the specified form templates for a deal.
  • list_form_templatesList form templatesGETReturns a list of your form templates. The form templates are returned sorted by creation date, with the most recent form templates appearing first.
  • list_lead_form_templatesList lead form templatesGETFetches the specified form templates for a lead.

Transaction, 3 operations

  • create_transactionCreate transactionPOSTRecords a customer transaction (amount in cents, ISO currency). Transactions drive revenue-based rewards for the referring partner. Reference the customer by customer_key, customer_external_key or customer_email.
  • delete_transactionDelete transactionDELETEDeletes a transaction.
  • list_transactionsList transactionsGETReturns a list of your transactions. The transactions are returned sorted by creation date, with the most recent transactions appearing first.

Reward, 2 operations

  • create_rewardCreate rewardPOSTCreates a reward (an amount in cents) on a customer, transaction or manual target. Rewards are paid out to partners, so this commits money.
  • list_rewardsList rewardsGETReturns a list of your rewards. The rewards are returned sorted by creation date by default, with the most recent rewards appearing first.

Base record export, 1 operation

  • export_base_recordsExport base recordsPOSTQueues an export of base records (partners, members, customers, transactions and more) that PartnerStack emails to member_email (or posts to webhook_target_url).

Deal file, 1 operation

  • list_deal_filesList deal filesGETLists the files attached to a deal (key, name, field_key). File downloads are not available through this integration.

Disti listing category, 1 operation

  • list_disti_listing_categoriesList disti listing categoriesGETLists the AppDirect-aligned category taxonomy used for distribution listings: each category's id, slug, display name and productLine.

Group, 1 operation

  • list_groupsList groupsGETReturns a list of your groups. The groups are returned sorted by creation date, with the most recent groups appearing first.

Partner team, 1 operation

  • get_partner_teamGet partner teamGETLists the members of a partner team (name, email, stack key) by the team's stack key.

Partner team member, 1 operation

  • add_partner_team_memberAdd partner team memberPOSTInvites or adds a member to a partnership's partner team; PartnerStack sends the invite from from_email (default the vendor owner). create_user true creates a user when none exists.

Partnership link, 1 operation

  • list_partnership_linksList partnership linksGETLists a partnership's referral links. identifier is the partner's email, partnership_key or partner_key.

Partnership tag, 1 operation

  • update_partnership_tagsUpdate partnership tagsPATCHAdds and removes tags on a partnership.

Report export, 1 operation

  • get_report_exportGet report exportGETGets a report export's status, file name, expiry and any error. The download link itself is not returned here; the export is emailed to the requesting teammate.

Stage, 1 operation

  • list_sales_cycle_stagesList sales cycle stagesGETRetrieves configured Sales Cycle Stages for a company or group (if group_key argument provided)

Tier collection, 1 operation

  • update_tier_collectionUpdate tier collectionPATCHUpdates a tier collection's name, active flag, cycle or tiers; only the fields sent change. Read the result with get_tier_collection.

Use PartnerStack from Claude Code, Cursor or Codex

Connect PartnerStack in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its PartnerStack operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect PartnerStack

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect PartnerStack once

    Add your PartnerStack connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

PartnerStack integration FAQ

What can you do with the PartnerStack integration?

LiveContext exposes 75 operations on PartnerStack, covering deal, lead, partnership and customer.

Popular integrations

Browse the whole catalog