> Toden documentation. For the full index fetch /llms.txt. Every page is available as Markdown by appending .md to its URL. Identity verification uses /api/kyc, Risk Intelligence uses /api/v1; they are separate contracts with different error shapes. Never invent an endpoint, field or enum value: read the API reference page for the operation first.

# Try it live

> The public workflow playground, the Sandbox, the API Explorer in these docs and the Toden Academy videos.

There are four ways to try Toden. The first needs no account at all.

#### [Playground](https://toden.co/playground)

Build a verification workflow and walk through it in your browser. No account.

#### [Sandbox](/get-started/sandbox-testing)

Run complete verifications with test IDs and receive real webhooks. Free.

#### [API Explorer](/api-reference/overview)

Send real requests from the reference pages with a test key.

#### [Toden Academy](/get-started/academy/overview)

Short videos from the console, each paired with its written guide.

## Which one to use

| You want to                           | Use          | Account needed      |
| ------------------------------------- | ------------ | ------------------- |
| See what an applicant goes through    | Playground   | No                  |
| Try the workflow builder and branding | Playground   | No                  |
| Test your own integration end to end  | Sandbox      | Yes                 |
| Check a request or response shape     | API Explorer | Yes, for a test key |
| Watch a feature being used            | Academy      | No                  |

## Playground

The playground is the real workflow builder, open to anyone at [toden.co/playground](https://toden.co/playground).

You configure a flow on one side and walk through it live on the other, exactly as an applicant would see it.

**What you can do**

* Start from a template.
* Pick countries and ID types.
* Set up the selfie and liveness step.
* Edit the welcome and success screens.
* Change the appearance, such as the brand colour and light or dark mode.
* Write simple decision rules.

**What it does not do**

* Nothing is uploaded and nothing is verified. Camera steps show a placeholder and submissions are simulated in the browser.
* No verification is created, no webhook is sent and nothing is charged.
* Some sections are shown but cannot be edited without an account, for example NFC chip reading, proof of address, questionnaires, AML screening and business verification. Reaching for one prompts you to sign up.
* Publishing, hosted links, prices, version history and results need an account.

> **Tip**
>
> Your draft is kept in your browser. If you create an account from the playground, the workflow you built is carried into it as you left it.

## Sandbox

The Sandbox is the full product with test data. Use it to prove your integration before you go live.

* Create an account at [console.toden.co](https://console.toden.co) and copy a test key (`pk_test_...` or `sk_test_...`).
* Sandbox identity verification accepts published test IDs. Each test ID produces a known outcome, so you can exercise approvals, declines and every failure reason.
* Webhooks fire as they do in production, so you can test your receiver.
* Sandbox verifications are free.

Start with [Sandbox and test IDs](/get-started/sandbox-testing). For a first run without code, follow the [hosted quickstart](/get-started/quickstart-hosted) to publish a workflow and open its link.

## API Explorer

Every endpoint page in the [API reference](/api-reference/overview) has an explorer. Pick an environment, paste a test key and send the request from the page.

> **Warning**
>
> A request sent from the explorer is a real request against the environment you select. Use test keys. Do not paste a live secret key into a browser.

The explorer is the quickest way to see an exact response body or an error shape before you write the call yourself.

## Toden Academy

The [Academy](/get-started/academy/overview) is a set of short videos recorded in the console. Each one is paired with the written guide for the same feature, so you can watch first and then follow the steps.

## Using an AI coding agent

If you would rather have an agent build the first version, see [Integrate with an AI agent](/get-started/ai/overview). It explains which contracts to give the agent and how to have it prove the result in Sandbox.

## Next steps

#### [Hosted quickstart](/get-started/quickstart-hosted)

Publish a workflow and send its link.

#### [SDKs](/integrate/sdks/overview)

Embed the flow in your web or mobile app.