> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reclack.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Quickstart
> Create a plan, open a checkout, and take a sandbox payment.
This walks through one complete payment in sandbox. Nothing here moves real
money, and the same calls work against live once you swap the key.
You need a Reclack account and a sandbox API key. Create one in the dashboard
under **Developers**, then **API keys**. Sandbox keys start with
`rk_sandbox_`.
Export the key so the examples below can use it.
```bash theme={null}
export RECLACK_KEY="rk_sandbox_your_key_here"
export RECLACK_API="https://api.reclack.com"
```
A product is what you sell. A price says how much it costs, how often it is
billed, and on which networks it can settle. You can create both in one
call.
```bash theme={null}
curl -X POST "$RECLACK_API/v1/products" \
-H "Api-Key: $RECLACK_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Pro Plan",
"description": "Everything in Starter, plus priority support",
"price": {
"amount": "29.00",
"cadence": "monthly",
"networks": ["base"]
}
}'
```
The response carries the product with its price nested inside. Keep the
price id: it is what a checkout session is built from.
Customers are how payments, invoices and subscriptions stay attached to a
person rather than to an address.
```bash theme={null}
curl -X POST "$RECLACK_API/v1/customers" \
-H "Api-Key: $RECLACK_KEY" \
-H "Content-Type: application/json" \
-d '{
"email": "dana@acme.dev",
"name": "Dana Okafor",
"external_id": "user_4821"
}'
```
`external_id` is your own identifier. Sending it means you can look a
customer up later without storing our id.
A checkout session is a hosted page your customer opens to pay. Pass the
price id and the networks you are willing to accept.
```bash theme={null}
curl -X POST "$RECLACK_API/v1/checkouts" \
-H "Api-Key: $RECLACK_KEY" \
-H "Content-Type: application/json" \
-d '{
"price_id": "price_2Pb8xk9",
"networks": ["base"],
"customer": { "email": "dana@acme.dev" },
"expires_in": 3600,
"metadata": { "plan": "pro" }
}'
```
The response includes a `url`. Open it in a browser to see exactly what
your customer sees.
The hosted page lists the wallets your browser exposes. Connect one on a
test network, approve the spending limit, and confirm the payment.
Sandbox runs on test chains, so you need test funds rather than real ones.
The page tells you which network it expects.
Create a webhook endpoint in the dashboard, then wait for the events. A
completed subscription checkout produces `checkout.completed`,
`payment.succeeded` and `subscription.created`.
```bash theme={null}
curl "$RECLACK_API/v1/events" \
-H "Api-Key: $RECLACK_KEY"
```
That endpoint lists everything Reclack has emitted for your workspace, which
is handy before your webhook handler exists.
## What you have now
A product with a price, a customer, a completed checkout, and a subscription
that will collect on its own schedule. From here:
What happens on every billing period, and what to do when one fails.
Verify the signature and act on events safely.
Swap the key, register a settlement address, and ship.
Every endpoint, with its parameters and responses.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.