canonical: https://jentic.com/apis/thrivecart.com/thrivecart

# ThriveCart API

The ThriveCart API provides access to products, customers, transactions, and event subscriptions (webhooks) for the ThriveCart shopping cart platform. All endpoints use POST and return JSON. Rate limited to 60 requests per minute per account. Authentication via API key (Bearer token) or OAuth 2 for third-party apps. The API exposes 16 endpoints secured with bearer, oauth2 authentication.

## For AI agents

Programmatically ping / connectivity test, list products. Covers 16 operations with bearer, oauth2 authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Ping / connectivity test
- List products
- Get a product
- Look up a customer
- Refund a transaction

## Use cases

### Payments Operations

Use the ThriveCart API to perform payments operations programmatically. The API provides 16 endpoints covering core functionality including ping / connectivity test, list products, get a product.

Example prompt: Call POST /ping to ping / connectivity test

### Automated Coupons Management

Automate coupons operations by combining multiple ThriveCart API endpoints. Agents can list products and then get a product in a single workflow.

Example prompt: Call POST /products to list products, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call ThriveCart API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer, oauth2 tokens manually.

Example prompt: Search Jentic for 'ping / connectivity test', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/ping` | Ping / connectivity test |
| POST | `/products` | List products |
| POST | `/products/{product_id}` | Get a product |
| POST | `/customers` | Look up a customer |
| POST | `/transactions` | List transactions |
| POST | `/transactions/{transaction_id}` | Get a transaction |
| POST | `/transactions/{transaction_id}/refund` | Refund a transaction |
| POST | `/subscriptions/{subscription_id}/cancel` | Cancel a subscription |

## Key resources

- **Coupons** — Operations for coupons
- **Customers** — Operations for customers
- **Embed** — Operations for embed
- **Ping** — Operations for ping
- **Products** — Operations for products

## Why Jentic

- **Setup:** Wiring the ThriveCart API by hand means choosing between its bearer token and OAuth2 authorization-code flow, then building the product, transaction, and subscription calls yourself. Through Jentic you install once, import the ThriveCart API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** ThriveCart puts the product, transaction, and subscription ids in the URL path (`/transactions/{transaction_id}`, `/subscriptions/{subscription_id}/cancel`), so a rule can pin your agent to one resource: it can read a specific transaction and nothing else. You choose the operations it may call, so destructive ones like refunding a transaction or cancelling a subscription are not included unless you add them.
- **Credential handling:** Your ThriveCart credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a product' or 'refund a transaction', and Jentic returns the matching ThriveCart API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the ThriveCart API use?

The ThriveCart API uses bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I ping / connectivity test with the ThriveCart API?

Yes. Use the POST /ping endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the ThriveCart API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I ping / connectivity test through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'ping / connectivity test'. Jentic returns the matching ThriveCart API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the ThriveCart API have?

The ThriveCart API exposes 16 endpoints covering coupons, customers, embed operations.

### Can I limit what my agent is allowed to do with the ThriveCart API?

Yes. Jentic One is self-hosted by you, so your own rules decide which ThriveCart operations and credentials your agent may use. Because ThriveCart puts resource ids in the URL path, such as `/transactions/{transaction_id}` and `/subscriptions/{subscription_id}/cancel`, you can pin the agent to a single resource, for example letting it read one specific transaction and nothing else. You also choose the operations it may call, so destructive ones like refunding a transaction or cancelling a subscription are excluded unless you add them.