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

# Test i sandkassen

> Peg Whop SDK og Elements mod sandkassen, opret test-API-nøgler og webhooks, simuler betalinger med testkort, og gennemgå sandkassens begrænsninger.

Whop stiller et sandkassemiljø til rådighed, så du kan teste din integration uden at påvirke produktionsdata eller foretage rigtige betalinger.

## Sandkasse-URL'er

| Miljø | URL |
| - | - |
| Frontend | `https://sandbox.whop.com` |
| API | `https://sandbox-api.whop.com/api/v1` |

Opret din sandkassekonto og dine API-nøgler på [sandbox.whop.com](https://sandbox.whop.com).

## Konfiguration af software development kit

For at bruge sandkassemiljøet med Whop SDK skal du angive miljøet `Sandbox`. Et miljø navngiver alle de hosts, SDK'et kommunikerer med, så alle requests flyttes til sandkassen på én gang.

```typescript TypeScript theme={null}
import { WhopClient, WhopEnvironment } from "@whop/sdk";

const client = new WhopClient({
	token: process.env["WHOP_API_KEY"],
	environment: WhopEnvironment.Sandbox,
});
```

```python Python theme={null}
import os
from whop_sdk import Whop, WhopEnvironment

client = Whop(
    token=os.environ.get("WHOP_API_KEY"),
    environment=WhopEnvironment.SANDBOX,
)
```

```ruby Ruby theme={null}
require "whop_sdk"

client = Whop_sdk::Client.new(
  token: ENV.fetch("WHOP_API_KEY"),
  environment: Whop_sdk::Environment::SANDBOX,
)
```

```rust Rust theme={null}
use whop_sdk::prelude::*;

let config = ClientConfig {
    token: Some(std::env::var("WHOP_API_KEY").unwrap()),
    base_url: "https://sandbox-api.whop.com/api/v1".to_string(),
    ..Default::default()
};
let client = Whop::new(config).expect("Failed to build client");
```

```go Go theme={null}
import (
    "os"

    whopsdk "github.com/whopio/whopsdk-go/v2"
    "github.com/whopio/whopsdk-go/v2/client"
    "github.com/whopio/whopsdk-go/v2/option"
)

client := client.NewWhop(
    option.WithToken(os.Getenv("WHOP_API_KEY")),
    option.WithEnvironment(whopsdk.Environments.Sandbox),
)
```

> [!NOTE]
>
> Miljøet `Sandbox` kom med SDK 2.0. På 1.x skal du i stedet pege klienten mod `https://sandbox-api.whop.com/api/v1`: `baseUrl` i TypeScript, `base_url` i Python og Ruby, `option.WithBaseURL` i Go. TypeScript, Ruby og Go beholder denne tilsidesættelse i 2.0, men den sender alle requests til én host. Operationer, der skal nå en anden host, afvises derefter, så brug `environment`. Python-klienten i 2.0 har ingen `base_url`-parameter. Rust-SDK'et er stadig 1.x og beholder `base_url`.

## Elements i sandkassen

For at pege [Whop Elements](https://docs.whop.com/da/elements/latest/getting-started.md) mod sandkassen skal du angive `environment`, når du opretter SDK-instansen. Denne option er den eneste måde at ændre, hvor elementerne sender det, en køber indtaster.

Elements-egenskaben til valg af en variant hedder stadig `plan` af kompatibilitetshensyn.

```tsx React theme={null}
import { WhopElements, Payments, PaymentElement, BrandingElement } from "@whop/elements-react";
import { loadWhop } from "@whop/elements";

function App() {
	return (
		<WhopElements elements={loadWhop()} environment="sandbox">
			<Payments accountId="biz_xxxxxxxxxxxxx" plan="plan_xxxxxxxxxxxxx">
				<PaymentElement />
				<BrandingElement />
			</Payments>
		</WhopElements>
	);
}
```

```html JavaScript theme={null}
<script src="https://cdn.whop.com/elements/amber/elements.js" data-whop-elements></script>
<script type="module">
  const whop = window.WhopElements({ environment: "sandbox" });
  const payments = whop.payments.create({
    accountId: "biz_xxxxxxxxxxxxx",
    plan: "plan_xxxxxxxxxxxxx",
  });
  payments.create("payment").mount("#payment");
  payments.create("branding").mount("#branding");
</script>
```

## Application programming interface-nøgler og webhooks

API-nøgler og webhooks fungerer på samme måde i sandkassen som i produktion:

* Opret API-nøgler på [sandbox.whop.com/dashboard/developer](https://sandbox.whop.com/dashboard/developer)
* Konfigurer webhooks til at modtage hændelser fra sandkassen
* Brug de samme autentificeringsheaders (`Authorization: Bearer YOUR_API_KEY`)

## Testkort

Brug følgende testkortnumre til at simulere betalinger i sandkassen:

| Kortnummer | Beskrivelse |
| - | - |
| `4242 4242 4242 4242` | Gennemført betaling |
| `4000 0000 0000 0002` | Afvist betaling |
| `4000 0000 0000 0341` | Opsætning af kortet lykkes, men betalingsbehandleren afviser senere opkrævninger |
| `5385 3083 6013 5181` | Kræver 3D Secure (indtast `Checkout1!` på 3DS-skærmen) |

I produktion har en afvist betaling en kode fra kortudstederen. [Forklaring af afvisningskoder for betalinger](https://docs.whop.com/da/payments-and-billing/payment-issues/payment-decline-reasons.md) viser, hvad hver enkelt betyder.

For alle testkort:

* Brug en vilkårlig fremtidig udløbsdato (f.eks. 12/34)
* Brug en vilkårlig 3-cifret kontrolkode (f.eks. 123)
* Brug en vilkårlig faktureringsadresse

Brug `4000 0000 0000 0341` til at teste genopretningsflows, hvor du gemmer et kort
med succes, men en fremtidig opkrævning på det gemte kort mislykkes.

## Betalingsmetoder i sandkassen

Brug [testkortene](#test-cards) ovenfor til at teste kortbetalinger.

Disse metoder kan også gennemføres i sandkassen via hver udbyders eget testflow: PayPal, Bancontact, iDEAL, Cash App Pay, Pix og Boleto.

Disse metoder understøttes endnu ikke i sandkassen:

* Apple Pay og Google Pay
* Bankkonti (ACH)
* SEPA Direct Debit
* EU-bankoverførsler og bankoverførsler (wire transfers)
* Alipay, WeChat Pay og MobilePay

## Kendte begrænsninger

> [!WARNING]
>
> Følgende funktioner er ikke tilgængelige i sandkassen:

* Udbetalinger
* Kryptoindbetalinger og on-chain-overførsler
* Discord-direkte beskeder og rollesynkronisering
* Opdaterede søgeresultater
* Visse planlagte og baggrundsjobs, der kører i produktion, såsom svindelgennemgange og opsummerings-e-mails
