> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/settings/integrations/how-to-integrate-quicksell-with-doubletick.md).
# How to Integrate QuickSell with DoubleTick
**Follow these simple steps to integrate your QuickSell account with DoubleTick and view your catalog in the chat section.**
**1. Login to QuickSell**
* **Go to QuickSell and log in to your account.**
**2. Generate API Key**
* **Navigate to Account Settings > Developer API.**
* **Click on Generate API Key.**
* **Once generated, copy the API key.**
**3. Login to DoubleTick**
Next, log in to your DoubleTick account by visiting [web.doubletick.io](https://web.doubletick.io/) and entering your login number.
**4. Paste API Key in DoubleTick**
**• Navigate to Settings > Integrations > Paste the copied API key into the appropriate field.**\
**> Click Connect to complete the integration.**
**5. Confirmation**
* **After the integration is complete, you should be able to see your QuickSell catalog in the chat section of DoubleTick.**
**Now, you can easily access and view all the products of your brand created in QuickSell directly within DoubleTick!**
---
# 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://learn.doubletick.io/settings/integrations/how-to-integrate-quicksell-with-doubletick.md?ask=&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.
