> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/integrations/loyalty-and-subscriptions/bold-recart-integration.md).

# BOLD <> Recart Integration

Shows how to connect Bold Subscriptions to Recart so you can manage recurring subscriptions from synced data.

Connecting Bold Subscriptions to Recart lets you sync your Recart subscribers with Bold so you can manage recurring subscriptions seamlessly.

It's easy to connect — all you have to do is copy your API key from **BOLD** and paste it into Recart. Here's how:

### In Bold Subscriptions

1. Log in to your Bold Subscriptions account
2. Expand the left-hand menu and select **API access tokens**
3. Select **Create API access token**

![Bold\_API\_Token-1](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FVLe7nB3SxcmDRcpBCiEm%2FBold_API_Token-1.png?alt=media)

4. Enter the **API access token name** and select the scopes you need
5. Select **Create. Important** **Note:** This API access token will **disappear** once the dialogue box closes. Copy your **API Token** and save it in a secure place
6. In the left-hand menu, go to **Settings**
7. Go to **Customer portal** and copy the URL from the **Admin customer portal link** field — this is your **Customer Portal Link.** By default it's set to pages/manage-subscriptions

### In Recart

1. Log in to your [Recart account](https://app.recart.com/)
2. Go to the [Integrations page](https://app.recart.com/integrations) in Recart
3. Find the Bold Subscriptions card and open it

![Integrations - List](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FBDtSd7BaR8TPSjdqPF1o%2FIntegrations%2520-%2520List.png?alt=media)

4. Paste the **API Token** and **Customer Portal Link** and click **Connect**

![Bold\_API](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FAw8wJSPYJXkTJMYuUUMy%2FBold_API.png?alt=media)

5. Once the connection is verified, you'll see a success message and the integration will switch to Active

![Integrations - Bold](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FwdXLnTZ8eJEN1blnSqxM%2FIntegrations%2520-%2520Bold.png?alt=media)

That's it — Bold Subscriptions is now connected to Recart, and your subscribers will sync automatically. 🎉

If you have any questions, do not hesitate to [contact the Recart Support team.](/contact-recart-support.md)  We'd be happy to help!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.recart.com/integrations/loyalty-and-subscriptions/bold-recart-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.