> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/~/revisions/x7Thkx1S9I9SnLbXNFwg/marketplaces/integration-onboarding-experiences-overview.md).

# Integration Onboarding Experiences Overview

Alongside our integration platform, we offer flexible, optional solutions to help you get your integrations adopted, while reducing the effort required to build and maintain onboarding flows.

**We offer three customizable, embeddable options for integration onboarding UIs and first-time user experiences:**

* [**In-App Marketplace**](/~/revisions/x7Thkx1S9I9SnLbXNFwg/marketplaces/integration-onboarding-experiences-overview/embedding-the-marketplace.md) – Embed a fully branded, white-labeled integration marketplace directly into your app.
* [**Embedded Integration Install**](/~/revisions/x7Thkx1S9I9SnLbXNFwg/marketplaces/integration-onboarding-experiences-overview/embedding-the-integration-install-only.md) – Embed a secure, fully managed integration setup UI into an existing marketplace.
* [**Embedded OAuth**](/~/revisions/x7Thkx1S9I9SnLbXNFwg/marketplaces/integration-onboarding-experiences-overview/embedding-auth-only-connections.md) – Embed an authentication pop-upin an existing marketplace. Allow users to securely connect to external systems without any manual configuration.

For all three options, Pandium handles OAuth flows and API key exchanges behind the scenes. Each can be embedded into your app or marketplace using an iframe.

**Watch the 2-minute video below to see these options in action:** 

{% embed url="<https://drive.google.com/file/d/1jIpANGh2z_FnF05V0EA3qdQ7-YrBmXoR/view?usp=sharing>" %}

&#x20;&#x20;

<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.pandium.com/~/revisions/x7Thkx1S9I9SnLbXNFwg/marketplaces/integration-onboarding-experiences-overview.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.