Integration

JVZoo integration

JVZoo is an affiliate marketplace for digital products. As a vendor, list and read your sales (v3.0 transactions with payouts, refunds and click attribution, plus the older v2.1 and v2.0 transaction routes), list your product names, read and set an affiliate's approval and commission for a product, and read or cancel a recurring payment; as an affiliate, read the latest transactions you referred. Buyer IP addresses, PayPal emails, delivery names, phones and postal addresses, referrer URLs and raw click query strings are not returned, and the affiliate stats route is not exposed because its response fields are undocumented. Every response uses one envelope: meta.status (http_status_code and a four-digit JVZoo code) and a results array. Authentication is HTTP Basic: the API key of a vendor application created at jvzoo.com under My Account, Applications as the username and the letter x as the password. The key grants full access to the JVZoo account.

Connect JVZoo How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with JVZoo

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.

Transaction, 5 operations

get_transactionGet transactionGETGet one of your sales by transaction_id (payKey from list_transactions), with buyer, affiliate, payouts, refund and click attribution. You must be the vendor of that transaction, else 404.
get_transaction_summaryGet transaction summaryGETOlder v2.0 summary of one transaction by paykey: date, product, status, price and buyer name. Prefer get_transaction or get_transaction_details for payouts and taxes.
list_latest_transactionsList latest transactionsGETList up to 100 of your sales across all your products, starting from your oldest transactions. To read the next 100, call list_latest_transactions_after with the last transaction_id.
list_latest_transactions_afterList latest transactions afterGETList up to 100 of your sales that come after the given paykey. Same as list_latest_transactions, continuing from a transaction.
list_transactionsList transactionsGETList your sales as a vendor between start_date and end_date, with buyer, affiliate, payouts, refund and click attribution. Page with page_index while meta.pagination.has_more is true.

Affiliate status, 3 operations

get_affiliate_statusGet affiliate statusGETGet the relationship of one affiliate with one of your products: approval status (REQUESTED, APPROVED or DENIED), commission rate, delayed commission and custom payouts.
get_affiliate_status_v2Get affiliate status v2GETOlder v2.0 shape of get_affiliate_status: status as a numeric status_id and commission as a decimal string. Prefer get_affiliate_status unless you need this shape.
set_affiliate_statusSet affiliate statusPUTApprove or deny an affiliate for one of your products and set their commission. Changes the affiliate's real access and payouts. Returns the updated relationship.

Affiliate transaction, 2 operations

list_affiliate_transactionsList affiliate transactionsGETList up to 100 transactions you referred as an affiliate, starting with the oldest from 90 days ago, with your commission. Continue with list_affiliate_transactions_after.
list_affiliate_transactions_afterList affiliate transactions afterGETList up to 100 transactions you referred as an affiliate that come after the given paykey. Same as list_affiliate_transactions, continuing from a transaction.

Recurring payment, 2 operations

cancel_recurring_paymentCancel recurring paymentPUTCancel a recurring payment for real by preKey: set status to CANCEL. The buyer's future payments stop. Returns canceled true on success.
get_recurring_paymentGet recurring paymentGETGet the status of a recurring payment by preKey (pre_key from get_transaction_details): status, payments made and remaining, amounts, next and last payment dates.

Detail, 1 operation

get_transaction_detailsGet transaction detailsGETGet the v2.1 details of a transaction by paykey: amounts, taxes, vendor, affiliate, buyer name, email and phone, and one payout row per payee. pre_key links a recurring payment.

Product, 1 operation

list_product_namesList product namesGETList the ids and names of your JVZoo products. Use product_id with get_affiliate_status and set_affiliate_status.

Use JVZoo from Claude Code, Cursor or Codex

Connect JVZoo in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its JVZoo 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 JVZoo

Create your workspace
Sign up free. Nothing to install.
Connect JVZoo once
Add your JVZoo connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.