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

# Opdatér eller slet en verificering

> Opdatér identitetsfelter før verificering, eller fjern en verificering helt.

## Opdatér en verificering

Opdatér felter på en verificering, som Whop endnu ikke har godkendt. Brug dette til at rette forudfyldte data, før brugeren gennemfører Know Your Customer (KYC)-verificering.

```bash cURL theme={null}
curl -X PATCH https://api.whop.com/api/v1/verifications/idpf_xxxxxxxxxxxxx \
  -H "Authorization: Bearer $WHOP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "first_name": "Janet",
    "last_name": "Smith"
  }'
```

### Felter, der kan opdateres

| Felt | Beskrivelse |
| - | - |
| `first_name` | Juridisk fornavn |
| `last_name` | Juridisk efternavn |
| `date_of_birth` | International Organization for Standardization (ISO)-dato |
| `country` | ISO alpha-2-landekode |
| `personal_address` | Bopælsadresseobjekt |
| `business_name` | Juridisk virksomhedsnavn |
| `business_address` | Registreret virksomhedsadresse |
| `business_structure` | Juridisk enhedsstruktur – alle værdier og deres lande i [Virksomhedsstrukturer](https://docs.whop.com/da/developer/verification/business-structures.md) |

> [!WARNING]
>
> Du kan ikke opdatere en verificering, der allerede er `approved`. Identitetsdataene låses, når de er verificeret. Slet den, og opret en ny, hvis du skal starte forfra.

## Slet en verificering

Fjern en verificering fra en konto. Whop beholder dataene, men frakobler verificeringen og fjerner den fra listen.

```bash cURL theme={null}
curl -X DELETE https://api.whop.com/api/v1/verifications/idpf_xxxxxxxxxxxxx \
  -H "Authorization: Bearer $WHOP_API_KEY"
```

```json Response theme={null}
{
  "id": "idpf_xxxxxxxxxxxxx",
  "deleted": true
}
```

Efter sletning skal du kalde `POST /api/v1/verifications` for at starte forfra med en ny verificering.

> [!NOTE]
>
> Sletning annullerer ikke en igangværende KYC-session – den fjerner verificeringslinket fra kontoen. Sessionen udløber af sig selv.

## Genstart en verificering

Hvis Whop afviste en brugers KYC-verificering, eller brugeren skal gøre den om, behøver du ikke at slette og genoprette den. Kald create med `restart: true`:

```bash cURL theme={null}
curl -X POST https://api.whop.com/api/v1/verifications \
  -H "Authorization: Bearer $WHOP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "biz_xxxxxxxxxxxxx",
    "kind": "individual",
    "restart": true
  }'
```

Dette opgiver den gamle session og giver dig en ny `session_url`.

## Godkendelse

Alle skrive-endpoints kræver en Account API-nøgle med scopet `identity:write`.

### Fejl

| Status | Besked | Hvornår |
| - | - | - |
| `400` | `Cannot update an approved verification.` | Profilen er allerede verificeret |
| `400` | `at least one field is required` | Tom request-body |
| `400` | `Whop can't support users in {place} because it is a sanctioned jurisdiction.` (kode `address_country_sanctioned`) | `personal_address` eller `business_address` ligger i et [sanktioneret land eller område](https://docs.whop.com/da/trust-and-safety/trust-safety-overview/sanctioned-countries.md) |
| `401` | — | Manglende eller ugyldig API-nøgle |
| `403` | — | API-nøglen mangler scopet `identity:write` |
| `404` | `Verification not found` | `idpf_`-ID'et findes ikke eller er ikke synligt |


## Related topics

- [Verificér brugeridentiteter med KYC](https://docs.whop.com/da/developer/verification/overview.md)
- [Håndtér verificerings-RFI'er](https://docs.whop.com/da/developer/verification/rfis.md)
- [Migrer fra ældre fakturaer](https://docs.whop.com/da/developer/guides/migrate-from-legacy-invoices.md)
