> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/dinmo-ingest/yotpo/setup-guide.md).

# Setup Guide

## Prerequisites <a href="#prerequisites" id="prerequisites"></a>

To connect Yotpo to DinMo, you need:

* a [Yotpo](https://www.yotpo.com/) account
* an app key

## Setup instructions <a href="#setupinstructions" id="setupinstructions"></a>

1. In the connection setup form, enter the **Destination schema** name of your choice.
2. Enter your **App key**.
3. Click **Authorize** to allow DinMo to access your Yotpo account using OAuth. You will be redirected to your Yotpo account to authorize DinMo's access.
4. Log in to your Yotpo account. Once you have finished, you will be redirected back to DinMo.
5. (Hybrid Deployment only) If your destination is configured for Hybrid Deployment, the Hybrid Deployment Agent associated with your destination is pre-selected in the **Select an existing agent** drop-down menu. To use a different agent, select the agent of your choice, and then select the same agent for your destination.
6. Click **Save & Test**. DinMo will take it from here and sync your data from your Yotpo account.

<br>


---

# 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://docs.dinmo.io/integrations/dinmo-ingest/yotpo/setup-guide.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.
