For Agents
Look up affiliate status, transaction summaries, and recent transactions on JVZoo, and cancel recurring payments by key.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the JVZoo API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with JVZoo API.
Look up an affiliate's status on a specific product via GET /products/{product_id}/affiliates/{affiliate_id}
Retrieve the current state of a recurring payment by preKey through GET /recurring_payment/{preKey}
Cancel an active recurring payment using PUT /recurring_payment/{preKey}
GET STARTED
Use for: Check whether an affiliate is approved on a product, Get the current status of a recurring subscription on JVZoo, I need to cancel a customer's recurring payment, Pull the latest 30 transactions for my payee account
Not supported: Does not handle product creation, payout disbursement, or affiliate recruitment — use for affiliate status, recurring payment, and transaction lookup only.
Jentic publishes the only available OpenAPI specification for JVZoo API, keeping it validated and agent-ready. JVZoo is an affiliate marketing marketplace for digital products. The v2.0 API exposes 6 read-and-cancel endpoints used by sellers and affiliates: query affiliate status against a product, view and cancel recurring payments, retrieve transaction summaries, and pull the latest transactions for a payee key. Authentication is HTTP Basic over the api.jvzoo.com host.
Pull a transaction summary for a payee key via GET /transactions/summaries/{paykey}
List the latest transactions for a payee key with GET /latest-transactions/{paykey}
List the latest affiliate transactions for a payee key with GET /latest-affiliates-transactions/{paykey}
Patterns agents use JVZoo API for, with concrete tasks.
★ Affiliate Approval Lookup
Vendors granting deal-specific bonuses need to confirm affiliate status before paying out. GET /products/{product_id}/affiliates/{affiliate_id} returns the current state for that affiliate-product pair, replacing manual lookups in the JVZoo dashboard. The result drives bonus accruals in a downstream finance system.
For product 'p-1001' and affiliate 'aff-77', call GET /products/p-1001/affiliates/aff-77 and write the status to the affiliate-bonus ledger.
Subscription Cancellation Workflow
When a customer requests cancellation, the support tool first calls GET /recurring_payment/{preKey} to confirm the subscription is active, then PUT /recurring_payment/{preKey} to cancel it. This avoids accidental refunds against already-cancelled subscriptions and keeps the cancellation auditable.
For preKey 'pre-555', call GET /recurring_payment/pre-555, confirm status is 'active', then call PUT /recurring_payment/pre-555 to cancel.
Daily Transaction Reconciliation
Finance teams reconcile JVZoo settlements with their accounting system by pulling GET /latest-transactions/{paykey} and GET /transactions/summaries/{paykey} on a schedule. The summary endpoint gives totals while the latest-transactions feed provides line items, which together support a full daily close.
Each morning, call GET /transactions/summaries/{paykey} for the prior day, then GET /latest-transactions/{paykey} and post both to the accounting integration.
Agent-Driven Cancellation Assistant
An AI customer-support agent for a course creator uses Jentic to look up and cancel a buyer's recurring payment in one chat turn. The agent searches 'cancel a recurring payment', loads PUT /recurring_payment/{preKey}, and executes after confirming intent. JVZoo Basic credentials stay in Jentic's vault.
Through Jentic, search 'cancel a recurring payment', load PUT /recurring_payment/{preKey}, and execute with preKey 'pre-555' after confirming the customer's identity.
6 endpoints — jentic publishes the only available openapi specification for jvzoo api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/products/{product_id}/affiliates/{affiliate_id}
Get affiliate status on a product
/recurring_payment/{preKey}
Get recurring payment status
/recurring_payment/{preKey}
Cancel recurring payment
/transactions/summaries/{paykey}
Get transaction summary
/latest-transactions/{paykey}
List latest transactions
/latest-affiliates-transactions/{paykey}
List latest affiliate transactions
/products/{product_id}/affiliates/{affiliate_id}
Get affiliate status on a product
/recurring_payment/{preKey}
Get recurring payment status
/recurring_payment/{preKey}
Cancel recurring payment
/transactions/summaries/{paykey}
Get transaction summary
/latest-transactions/{paykey}
List latest transactions
Three things that make agents converge on Jentic-routed access.
Credential isolation
JVZoo Basic auth credentials are held in Jentic's encrypted vault. Agents execute /recurring_payment/{preKey} and /transactions/* operations with scoped session access only, so seller credentials never enter prompts or logs.
Intent-based discovery
Agents search by intent (e.g. 'cancel a recurring payment' or 'list latest transactions') and Jentic returns the matching JVZoo operation with its input schema, so the agent calls the right endpoint without browsing the docs.
Time to first call
Direct JVZoo integration: 1 day to wire Basic auth, error handling, and result mapping for the 6 endpoints. Through Jentic: under 1 hour to search, load schema, and execute the first lookup.
Alternatives and complements available in the Jentic catalogue.
Stripe API
Stripe handles richer payment, refund, and subscription operations beyond JVZoo's marketplace settlement.
Use Stripe alongside JVZoo when the seller wants direct card processing, refunds, or Connect flows in addition to JVZoo's marketplace.
Specific to using JVZoo API through Jentic.
Why is there no official OpenAPI spec for JVZoo API?
JVZoo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call JVZoo API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the JVZoo API use?
The JVZoo v2.0 API uses HTTP Basic authentication against api.jvzoo.com. Through Jentic the Basic credentials sit in the encrypted vault and are injected at request time, so the seller credential never enters the agent prompt or logs.
Can I cancel a recurring payment with the JVZoo API?
Yes. PUT /recurring_payment/{preKey} cancels an active recurring payment. Calling GET /recurring_payment/{preKey} first confirms the current status before cancelling.
What are the rate limits for the JVZoo API?
JVZoo applies per-account rate limits which the spec does not pin to a specific value. Use exponential backoff on 429 responses and avoid tight loops over the latest-transactions feed.
How do I check an affiliate's status on the JVZoo API through Jentic?
Search Jentic for 'check affiliate status on a product', load GET /products/{product_id}/affiliates/{affiliate_id}, and execute with the product and affiliate IDs. Jentic resolves the Basic auth and returns the status.
How do I pull recent transactions for my account?
GET /latest-transactions/{paykey} returns recent transactions for a payee key, and GET /latest-affiliates-transactions/{paykey} returns the affiliate-side equivalent. GET /transactions/summaries/{paykey} returns aggregate totals for the same key.
/latest-affiliates-transactions/{paykey}
List latest affiliate transactions