> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mythos.new/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mythos.new/_mcp/server.

# Connect your app to Paddle

> Connect your own Paddle account to work with products, customers, transactions, and subscriptions.

[Paddle](https://www.paddle.com/) provides billing for software and digital products. The Mythos connector uses an API key from your own Paddle account so you can build tools around its catalog, customers, transactions, and subscriptions.

You can use the connection while building in the project chat and in the app you publish. You manage the Paddle account, seller verification, checkout configuration, and billing terms in Paddle.

## What you can build

The connection supports reading products, prices, customers, transactions, subscriptions, and adjustments. With the appropriate key permissions, it also supports catalog changes, customer updates, transaction billing, subscription changes, and refunds or credits.

Start with a specific outcome, for example:

> Build a Paddle dashboard showing customers, their subscriptions, and recent transactions. Add filters for status and product.

> Show our existing Paddle products and prices on a pricing page. Let me review the displayed details before adding purchase actions.

> Build a support view that shows a customer's subscription and opens the Paddle customer portal for that customer after checking their identity.

These prompts ask Mythos to build an app. Saving the connection does not create a payment dashboard, checkout, customer access rules, or subscription entitlements automatically.

## Before you connect

You need:

* A Paddle account for the environment you intend to use.
* A Paddle API key with **`customer.read`**, required to check the connection.
* Read or write permissions for each additional area your app needs.
* Permission to create connections in your Mythos workspace.

Use **Sandbox** while developing a flow that could create charges or change subscriptions. Paddle Sandbox and Live have separate credentials and data. A sandbox key cannot be used with the live API host, or the other way around.

Your Paddle agreement governs provider charges and payment processing. Connecting an account to Mythos does not create a new seller account or complete Paddle's verification process for you.

## Connect your Paddle account

### 1. Create the API key

In the intended Paddle environment, open **Developer tools → Authentication → API keys** and create a key. Give it a clear name, choose permissions for your app, set its expiry, and copy the value securely.

Include `customer.read` for setup. A catalog dashboard also needs the relevant product and price reads; billing a transaction needs `transaction.write`. Grant write permissions only for actions you intend to support.

Use an **API key**, not a Paddle client-side token. These are different credentials. See Paddle's [authentication guide](https://developer.paddle.com/api-reference/about/authentication/) for key creation and permissions.

### 2. Save it in Mythos

1. From the Dashboard, open **Connectors** and select **Paddle**. If no saved connection is available, the setup form opens.
2. Enter a **Display name** that identifies its purpose and environment, such as `Billing sandbox`.
3. Paste the key into **API key**. Do not put it in a chat message.
4. In **API host**, select **Sandbox** or **Live** to match the environment that issued the key.
5. Under **Sharing**, keep **Private** or choose **Share with others**. Grant access to selected members, or choose **Share with workspace**.
6. Click **Connect Paddle**. Mythos checks customer read access before saving the connection.

To use it in an app, open **Chat actions (+) → Project connectors**, select the saved Paddle connection, and choose **Use in this project**. Then ask Mythos to build the feature you want. If the correct account is already connected and shared with you, use that connection. See [Connections in Mythos](/integrations/introduction) for access and project links.

## Test the intended behavior before using Live

The selected connection determines the Paddle environment. Publishing a Mythos app does not automatically switch Sandbox to Live, copy products and prices, or turn sandbox data into live data.

For a billing workflow, begin in Sandbox and check the user-facing result: the correct product and price, the intended customer, successful and failed payments, and the access the app should grant afterward. If you add subscription changes, also check cancellations and when those changes take effect.

Before moving to Live, complete the necessary account and checkout setup in Paddle. Use a live key with the **Live** API host and the live products and prices. Ask Mythos to update the app for those live resources. Keep the environment clear when discussing billing actions.

The connector can change subscriptions and create financial adjustments, so a support tool should clearly show the customer, amount, and action before applying them. It can also preview supported price and subscription changes before those changes are submitted.

## Limits and connection problems

Mythos does not provision your Paddle account, verify checkout domains, create client-side tokens, or register new notification destinations through this connector. Complete those settings in Paddle when your payment flow requires them.

If the connection fails, check the key's environment, expiry, and `customer.read` permission. If the connection works but a particular feature fails, check the permission for that area. Reading customers does not prove that transactions can be billed or subscriptions changed.

A customer portal link must be given only to the intended customer. Tell Mythos how the app should identify that person and connect them to the correct Paddle customer record.

## Manage the connection

Open **Connectors → Paddle**, then the saved connection. **Linked projects → Unlink projects** removes selected project links. **Disconnect** stops Mythos from using the connection; it does not close the Paddle account, cancel subscriptions, or refund payments. Manage any continuing billing directly in Paddle.

If you replace the key or change environments, disconnect the old connection and connect Paddle again with the intended key and matching **API host**. Link it to the projects that should use it, ask Mythos to set up the affected features again, and publish. Features using the disconnected connection stop working until they are set up again.