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

> ## Agent Instructions
> Treat these docs and the Whop MCP server as the source of truth for Whop API behavior. Don't infer endpoint behavior from marketing pages.
> MCP server: connect https://mcp.whop.com/mcp (streamable HTTP, browser sign-in, no API key in the client config) to search these docs and read or change live Whop data. Setup: https://docs.whop.com/developer/guides/ai_and_mcp.md
> Whop CLI: install with `curl -fsSL https://whop.com/install.sh | sh` to scaffold, run, and deploy Whop apps and websites. It acts on production, not the sandbox. Overview: https://docs.whop.com/cli/overview.md Agent mode: https://docs.whop.com/cli/agent-mode.md
> Hosting: Whop serves a site or app from the build `whop apps deploy` uploads, with rollbacks, secrets, and server logs. Guide: https://docs.whop.com/developer/websites/hosting.md
> Plugins: in Claude Code, run `/plugin marketplace add whopio/plugins`, then `/plugin install whop@whop`. Guide: https://docs.whop.com/developer/guides/plugins/claude-code.md Every agent tool: https://docs.whop.com/developer/ai/overview.md
> Environments: build and test in the sandbox (API `https://sandbox-api.whop.com/api/v1`, keys at https://sandbox.whop.com/dashboard/developer, SDK environment `Sandbox`; no real money). Production (API `https://api.whop.com/api/v1`, keys at https://whop.com/dashboard/developer, SDK environment `Production`, the SDK default) moves real money, so use it only at launch. The two share no accounts, keys, products, or webhooks, and their keys look identical: never mix them. Sandbox guide: https://docs.whop.com/developer/guides/sandbox.md Comparison: https://docs.whop.com/developer/quickstart.md
> API: send `Authorization: Bearer <API_KEY>` from your server only, and pin a dated version with the `Api-Version-Date` header. OpenAPI spec: https://api.whop.com/api/v1/openapi.json
> Which API: build on the Current API, whose pages live under https://docs.whop.com/api-reference/ (start at https://docs.whop.com/api-reference/overview.md). Pages under /api-reference/legacy/ are the Legacy API. Use one only when https://docs.whop.com/api-reference/stability.md lists the resource as Legacy-only.

# Godkendelse til chat

> Godkend brugere til indlejret chat med kontoafgrænsede tokens eller OAuth

> [card] [Whops typer af legitimationsoplysninger](https://docs.whop.com/da/developer/guides/auth-scoping.md)
>
> Se Godkendelse og API-nøgler for alle Whops typer af legitimationsoplysninger, hvornår du skal bruge hver af dem, og hvordan du begrænser et token til de handlinger, det har brug for.

Før du bruger chat-SDK'et, skal du godkende brugere. Vælg en af to tilgange:

| Tilgang | Bedst til |
| - | - |
| **[Kontoafgrænsede brugertokens](#account-scoped-user-tokens)** | Apps, der allerede har deres egne brugere. Din server udsteder Whop-tokens til dem uden et login-trin. |
| **[OAuth](https://docs.whop.com/da/developer/guides/chat/oauth.md)** | Apps, der vil have brugerne til selv at logge ind på Whop via en login-side eller et webview. |

## Kontoafgrænsede brugertokens

Brug denne tilgang, hvis **din app allerede har sine egne brugere** (via dit eget godkendelses-/sessionssystem). Du beholder dit eksisterende login-forløb og udsteder et Whop-token til den bruger, der aktuelt er logget ind — uden ekstra login-trin.

Din server veksler efter behov din Whop API-nøgle til et kortlivet brugertoken og returnerer det til klienten. Du bestemmer, hvilken bruger tokenet er til.

### Saml dine legitimationsoplysninger

Du skal bruge tre ting:

1. **API-nøgle** — opret en i [Whop Developer Dashboard](https://whop.com/dashboard/developer). Behandl den som en adgangskode, og hold den kun på din server.
2. **Konto-ID**. Find det i dit dashboards URL: `whop.com/dashboard/biz_XXXXXXXXX/`.
3. **Bruger-ID** — den bruger, du vil godkende. I produktion skal du udlede det fra dit eget godkendelses-/sessionssystem.

> [!NOTE]
>
> Til indlejret chat kræves både `account_id` og `user_id` sammen, når du udsteder et token.

### Opret et token-endpoint på din server

Tilføj et endpoint, der kalder `POST https://api.whop.com/api/v1/access_tokens` med din API-nøgle og returnerer det resulterende token til klienten.

> [tab] Next.js
>
> ```typescript app/api/chat/token/route.ts theme={null}
> import { NextResponse } from "next/server";
> import { WhopClient } from "@whop/sdk";
>
> const client = new WhopClient({ token: process.env.WHOP_API_KEY });
>
> export async function POST() {
>   // Derive these from your own auth / session in production.
>   const user_id = "user_XXXXXXXXXXXX";
>   const account_id = "biz_XXXXXXXXXXXXX";
>
>   const { token } = await client.accessTokens.create({
>     account_id,
>     user_id,
>     scoped_actions: [
>       "chat:message:create",
>       "chat:read",
>       "dms:read",
>       "dms:message:manage",
>       "dms:channel:manage",
>       "support_chat:read",
>       "support_chat:message:create",
>     ],
>   });
>
>   return NextResponse.json({ token });
> }
> ```

> [tab] Express
>
> ```typescript server.ts theme={null}
> import express from "express";
> import { WhopClient } from "@whop/sdk";
>
> const app = express();
> app.use(express.json());
>
> const client = new WhopClient({ token: process.env.WHOP_API_KEY });
>
> app.post("/api/chat/token", async (_req, res) => {
>   // Derive these from your own auth / session in production.
>   const user_id = "user_XXXXXXXXXXXX";
>   const account_id = "biz_XXXXXXXXXXXXX";
>
>   const { token } = await client.accessTokens.create({
>     account_id,
>     user_id,
>     scoped_actions: [
>       "chat:message:create",
>       "chat:read",
>       "dms:read",
>       "dms:message:manage",
>       "dms:channel:manage",
>       "support_chat:read",
>       "support_chat:message:create",
>     ],
>   });
>
>   res.json({ token });
> });
>
> app.listen(3000);
> ```

> [tab] cURL
>
> ```bash theme={null}
> curl -X POST https://api.whop.com/api/v1/access_tokens \
>   -H "Authorization: Bearer $WHOP_API_KEY" \
>   -H "Content-Type: application/json" \
>   -d '{
>     "account_id": "biz_XXXXXXXXXXXXX",
>     "user_id": "user_XXXXXXXXXXXX",
>     "scoped_actions": [
>       "chat:message:create",
>       "chat:read",
>       "dms:read",
>       "dms:message:manage",
>       "dms:channel:manage",
>       "support_chat:read",
>       "support_chat:message:create"
>     ]
>   }'
> ```

### Hent tokenet fra din app

Giv SDK'et en token-callback, der henter fra dit endpoint. Chatelementerne kalder den, hver gang de skal godkende, og igen automatisk, når tokenet udløber.

> [tab] React
>
> ```typescript theme={null}
> async function getToken() {
>   const response = await fetch("/api/chat/token", { method: "POST" });
>   const data = await response.json();
>   return data.token;
> }
> ```

> [tab] Vanilla JS
>
> ```typescript theme={null}
> async function getToken() {
>   const response = await fetch("/api/chat/token", { method: "POST" });
>   const data = await response.json();
>   return data.token;
> }
> ```

> [tab] Swift
>
> ```swift theme={null}
> import WhopElements
>
> class WhopAPITokenProvider: WhopTokenProvider {
>     private let serverURL = URL(string: "https://your-server.com")!
>
>     func getToken() async -> WhopTokenResponse {
>         do {
>             var req = URLRequest(url: serverURL.appendingPathComponent("api/chat/token"))
>             req.httpMethod = "POST"
>
>             let (data, _) = try await URLSession.shared.data(for: req)
>             let json = try JSONSerialization.jsonObject(with: data) as! [String: Any]
>             return WhopTokenResponse(accessToken: json["token"] as? String ?? "")
>         } catch {
>             return WhopTokenResponse(accessToken: "")
>         }
>     }
> }
> ```
>
> Giv token-provideren til SDK'et, når appen starter:
>
> ```swift theme={null}
> .task {
>     await WhopSDK.configure(tokenProvider: WhopAPITokenProvider())
> }
> ```

### Påkrævede scopes

Anmod om disse scopes, når du opretter tokenet:

| Scope | Formål |
| - | - |
| `chat:message:create`, `chat:read` | Kanaler |
| `dms:read`, `dms:message:manage`, `dms:channel:manage` | Direkte beskeder |
| `support_chat:read`, `support_chat:message:create` | Supportchats |

> [!NOTE]
>
> Hvis din app ejer brugerkontiene og udsteder kontoafgrænsede chattokens, skal du synkronisere disse brugere, før du angiver deres `user_id` her. Brugersynkronisering er ikke en del af OAuth.

> [card] [Synkroniser dine brugere](https://docs.whop.com/da/developer/guides/chat/sync-users.md)
>
> Opret eller tilknyt Whop-brugere, før du udsteder kontoafgrænsede chattokens.

## OAuth

OAuth har sin egen side, så denne guide kan holde fokus på kontoafgrænsede brugertokens.

Brug OAuth, når din app vil have brugerne til selv at logge ind på Whop via en login-side eller et iOS-webview. Det er det rigtige valg, når din app har brug for adgang til en Whop-konto, som brugeren ejer, eller når du ikke vil have din backend til at udstede Whop-brugertokens.

> [card] [OAuth](https://docs.whop.com/da/developer/guides/chat/oauth.md)
>
> Opsæt OAuth-scopes, redirect-URI'er, token-endpoints til web og SDK-administreret OAuth på iOS.


## Related topics

- [Quickstart til chat](https://docs.whop.com/da/developer/guides/chat/quickstart.md)
- [OAuth til chat](https://docs.whop.com/da/developer/guides/chat/oauth.md)
- [Synkroniser brugere til indlejret chat](https://docs.whop.com/da/developer/guides/chat/sync-users.md)
