# Strawberry ID — developer documentation (plain text)

These files are served as static assets alongside the web app so search engines, CLI tools, and IDEs can read **full examples and request bodies** without executing JavaScript.

## Merchant backend env template

Merchant integration is server-to-server. Use API bearer secrets (`sk_test_*`, `sk_live_*`) and a webhook secret per endpoint.

Suggested backend `.env`:

```dotenv
STRAWBERRY_API_BASE_URL=https://www.strawberryid.com/api
STRAWBERRY_API_KEY=sk_test_...
STRAWBERRY_WEBHOOK_SECRET=...
```

Optional split by mode:

```dotenv
STRAWBERRY_TEST_API_KEY=sk_test_...
STRAWBERRY_LIVE_API_KEY=sk_live_...
```

Reference file: [merchant-backend.env.example](./merchant-backend.env.example).

`ONE_WALLET_*` names are not required by Strawberry. If your codebase already uses those names, map them to the values above in your own config layer.

## Canonical API base URL

Use the host where your Strawberry ID deployment serves `/api`. Production is typically:

`https://www.strawberryid.com/api`

If your integration sandbox cannot resolve the apex domain (`strawberryid.com`), prefer the **www** host above or the exact base URL shown in your merchant dashboard.

## Index

| Topic | File |
| --- | --- |
| Merchant sandbox quickstart | [quickstart.md](./quickstart.md) |
| Routes, auth, and JSON bodies | [api-overview.md](./api-overview.md) |
| One Wallet payments & merchant refunds | [payments-refunds.md](./payments-refunds.md) |
| Signed webhooks | [webhooks.md](./webhooks.md) |
| Minimal HTTP clients | [client-examples.md](./client-examples.md) |
| OpenAPI 3 (machine-readable) | [/openapi/merchant-v1.openapi.json](../openapi/merchant-v1.openapi.json) |

## Interactive docs

The in-app developer hub (same content, styled) lives at:

`https://www.strawberryid.com/docs`