> ## Documentation Index
> Fetch the complete documentation index at: https://docs.frankieone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrating with FrankieOne

> FrankieOne offers multiple ways to integrate, depending on your technical requirements and desired level of control. This page outlines the core integration options and resources available.

## Choose your integration approach

FrankieOne offers multiple integration paths depending on your technical requirements and how much control you need over the user experience.

| Approach            | Best for                 | Effort | Control        |
| ------------------- | ------------------------ | ------ | -------------- |
| **Hosted OneSDK**   | Fast launch, minimal dev | Low    | Low            |
| **Embedded OneSDK** | Custom web UX            | Medium | High           |
| **Native OneSDK**   | iOS / Android apps       | Medium | High           |
| **API**             | Full backend control     | High   | Full           |
| **Portal**          | Ops teams, no-code       | None   | Dashboard only |

> **Not sure?** Most teams start with the **API and Portal** for the fastest path to production.

## Integration resources

<Columns cols={2}>
  <Card title="Portal" icon="credit-card" horizontal href="/docs/getting-started-with-the-frankieone-portal">
    Manage daily onboarding and compliance tasks through the FrankieOne Portal.
  </Card>

  <Card title="API" icon="terminal" horizontal href="/v2/api/introduction/introduction-to-frankie-one-api">
    FrankieOne’s API provides maximum flexibility for a custom onboarding experience.
  </Card>

  <Card title="Hosted OneSDK Solution" icon="laptop-code" horizontal href="/docs/quickstart-guide/use-case-1-hosted-onesdk">
    Use hosted OneSDK for a fully managed, low-code onboarding experience.
  </Card>

  <Card title="Embedded OneSDK Solution" icon="laptop-code" horizontal href="/docs/embedded-flows/quick-start">
    Embed OneSDK directly into your application to enable a custom verification experience.
  </Card>

  <Card title="Native App OneSDK Solution" icon="laptop-code" horizontal href="/docs/native-integration">
    Embed OneSDK directly into your application to enable a custom verification experience.
  </Card>

  <Card title="Webhook Notifications" icon="code-branch" horizontal href="/docs/notifications-and-webhooks">
    Set up real-time notifications for key verification and entity events via webhooks.
  </Card>

  <Card title="Test Data" icon="database" horizontal href="/docs/test-data">
    Use test data and sandbox environments to develop and validate your integration safely.
  </Card>
</Columns>

## Next steps

Once you've chosen your integration approach and set up your environment:

1. [Authenticate your API credentials](/docs/reference/authentication) to connect to FrankieOne.
2. Follow the [Quick Start Guide](/docs/getting-started) to make your first verification call.
3. Use [test data](/docs/test-data) in the sandbox environment to develop and validate your integration.