> ## 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.

# Identitetsdokumenter

> Hvilke identitetsdokumenter API'et accepterer, og de præcise filnøgler, der skal sendes for hvert af dem.

Verificér en person udelukkende via API'et ved at sende fotos af personens identitetsdokument i [Create Verification](https://docs.whop.com/da/api-reference/verifications/create-verification.md)-anmodningen. Ingen hostet session, ingen opfølgende kald: én `POST`, og derefter poller du efter afgørelsen.

## Hvilke filer der skal sendes

Vælg den `document_type`, der matcher dokumentet på fotoet. Den afgør præcis, hvilke nøgler `documents`-objektet skal indeholde – hverken mere eller mindre.

| `document_type` | Påkrævede `documents`-nøgler |
| - | - |
| `id_card` | `id_card_front`, `id_card_back`, `selfie` |
| `drivers` | `drivers_front`, `drivers_back`, `selfie` |
| `residence_permit` | `residence_permit_front`, `residence_permit_back`, `selfie` |
| `passport` | `passport_front`, `selfie` |

Hver værdi er filens rå bytes, base64-kodet:

```python theme={null}
import base64

def b64(path):
    with open(path, "rb") as f:
        return base64.b64encode(f.read()).decode()
```

## Filregler

* Joint Photographic Experts Group (JPEG), Portable Network Graphics (PNG) eller PDF. Whop registrerer typen ud fra filens faktiske bytes, så filtypenavnet er ligegyldigt.
* `selfie` skal være et JPEG- eller PNG-foto af personens ansigt.
* Maksimalt 5 MB pr. fil, målt før kodning.
* Send hele sættet i én anmodning. En manglende, for stor eller ulæselig fil får hele anmodningen til at fejle med en fejl, der nævner den præcise nøgle – ret den fil, og send den samme anmodning igen. Der indsendes aldrig noget delvist.

## Fuldt eksempel

```bash theme={null}
curl -X POST "https://api.whop.com/api/v1/verifications?account_id=biz_XXXXXXXX" \
  -H "Authorization: Bearer $WHOP_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{
    \"first_name\": \"Jane\",
    \"last_name\": \"Doe\",
    \"date_of_birth\": \"1990-01-01\",
    \"country\": \"US\",
    \"phone\": \"+15551234567\",
    \"tax_identification_number\": \"123456789\",
    \"address\": { \"line1\": \"123 Main St\", \"city\": \"Austin\", \"state\": \"TX\", \"postal_code\": \"73301\" },
    \"business_website\": \"https://example.com\",
    \"document_type\": \"drivers\",
    \"documents\": {
      \"drivers_front\": \"$(base64 -i front.jpg)\",
      \"drivers_back\": \"$(base64 -i back.jpg)\",
      \"selfie\": \"$(base64 -i selfie.jpg)\"
    }
  }"
```

En `201` betyder, at Whop har accepteret alle dokumenter og startet gennemgangen – svarets `required_documents` angiver hver nøgle som `submitted`. Poll [Retrieve Verification](https://docs.whop.com/da/api-reference/verifications/retrieve-verification.md), indtil `status` bliver `approved` eller `rejected`.

> [!NOTE]
>
> `business_website` er valgfri. Når den udelades, bruges kontoens whop.com-side til opsætning af udbetalinger. Hvis du sender en, skal det være et eksternt websted eller et link til sociale medier. Whop-butikssider afvises.

## Hvis Whop afviser et dokument

Når korrekturlæseren ikke kan acceptere et foto, vender `status` tilbage til `action_required`, og de afviste nøgler vises i `required_documents` som `pending_upload` med en `rejection_reason`. Send den samme Create Verification-anmodning igen med et bedre foto – gennemgangen genoptages automatisk.

## Landedækning

Whop accepterer `id_card`, `drivers` og `passport` for personer i de fleste lande. Tabellen nedenfor viser undtagelserne. For et land i denne tabel virker kun de angivne værdier. Alt andet kommer tilbage gennem det foregående afvisningsforløb.

| Land | Accepterede `document_type`-værdier |
| - | - |
| `AD` | `drivers`, `residence_permit`, `passport` |
| `AI` | `drivers`, `passport` |
| `AQ` | `passport` |
| `AS` | `drivers`, `passport` |
| `CC` | `id_card`, `passport` |
| `CK` | `drivers`, `passport` |
| `CX` | `drivers`, `passport` |
| `EH` | `passport` |
| `ER` | `id_card`, `passport` |
| `FK` | `passport` |
| `FM` | `drivers`, `residence_permit`, `passport` |
| `FO` | `drivers`, `passport` |
| `GF` | `id_card`, `residence_permit`, `passport` |
| `GL` | `drivers`, `passport` |
| `HM` | `passport` |
| `KY` | `drivers`, `passport` |
| `MS` | `drivers`, `residence_permit`, `passport` |
| `NF` | `passport` |
| `PM` | `id_card`, `passport` |
| `SH` | `passport` |
| `SJ` | `passport` |
| `TF` | `passport` |
| `TK` | `drivers`, `passport` |
| `TV` | `drivers`, `passport` |
| `VA` | `passport` |
| `WF` | `id_card`, `passport` |
| `YT` | `id_card`, `passport` |

Whop accepterer også `residence_permit` i de fleste lande, men dækningen er snævrere. Ud over den foregående tabel accepterer Whop den **ikke** for personer i:

`AG`, `AW`, `BB`, `BF`, `BI`, `BL`, `BZ`, `CV`, `CW`, `DM`, `GG`, `GI`, `GN`, `GS`, `GU`, `GY`, `IM`, `IO`, `JE`, `KI`, `KM`, `LC`, `LR`, `MF`, `ML`, `MP`, `MQ`, `MU`, `NC`, `NR`, `NU`, `NZ`, `PF`, `PG`, `PN`, `PR`, `PS`, `PW`, `SB`, `SC`, `SM`, `SR`, `ST`, `SX`, `SY`, `SZ`, `TC`, `TL`, `TO`, `VC`, `VI`, `WS`

Whop tilbyder ikke identitetsverificering til personer i disse lande og afviser alle dokumenttyper:

`AF` (Afghanistan), `BY` (Hviderusland), `CU` (Cuba), `HT` (Haiti), `IQ` (Irak), `IR` (Iran), `KP` (Nordkorea), `LY` (Libyen), `MM` (Myanmar), `MZ` (Mozambique), `RU` (Rusland), `SD` (Sudan), `SO` (Somalia), `SS` (Sydsudan)

> [!NOTE]
>
> Denne tabel afspejler Whops verificeringskonfiguration pr. juli 2026. Landeaccept anvendes under gennemgangen, så en dokumenttype, der ikke er gyldig for personens land, fejler med en `rejection_reason` i stedet for en fejl på forhånd.


## Related topics

- [Håndtér verificerings-RFI'er](https://docs.whop.com/da/developer/verification/rfis.md)
- [API-versioner](https://docs.whop.com/da/developer/api/versioning.md)
