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

# Choose an Integration

> Use the hosted OIDC flow for the fastest integration, or the REST API when you need your own UI.

Both methods use the same [connections](/v2/guides/concepts/connections), [workflows](/v2/guides/verifications/workflows), and returned data. They differ in who owns the user interface.

<Columns cols={2}>
  <Card title="Hosted OIDC" icon="id-card" href="/v2/guides/oidc-integration">
    Redirect the user to Hopae. Hopae runs country and provider selection and every flow type, then returns a code. **Start here.**
  </Card>

  <Card title="REST API" icon="code" href="/v2/guides/api-integration">
    Your backend creates the verification and your UI shows the QR code, redirect, or waiting screen for each flow type.
  </Card>
</Columns>

| | Hosted OIDC | REST API |
| :- | :- | :- |
| **User interface** | Hosted by Hopae, with your [branding](/v2/guides/concepts/branding) | Yours |
| **Flow types** | All handled for you | You handle each `flowType` |
| **Result** | Authorization code → token → `/userinfo` | Poll status → `/userinfo` |
| **Libraries** | Any OIDC client library | Plain HTTP |
| **Effort** | Low | Higher |

<Tip>
  Building a native app or embedding Hopae in your own IDV SDK? Your backend calls Hopae. The app only performs the user step. See [Mobile App Integration](/v2/guides/mobile-app-integration).
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.