Onboarding
2 Onboarding routes on the FLAM API: First-workflow checklist progress; Complete a checklist step (idempotent).
Base URL https://api.flam.fashion. Send Authorization: Bearer flam_sk_… on every call; a handful of routes are session-only and say so. How keys and roles work.
GET /api/toolkit/onboarding
First-workflow checklist progress
Responses
| Status | Meaning |
|---|---|
200 | Progress + reward state |
401 | No valid session |
200 returns:
{
"steps": {},
"completed": 0,
"total": 0,
"reward": {
"total": 0,
"granted": true
}
}Call it
curl -X GET "https://api.flam.fashion/api/toolkit/onboarding" \
-H "Authorization: Bearer $FLAM_API_KEY"POST /api/toolkit/onboarding
Complete a checklist step (idempotent)
Completing the last step mints a one-time 30-token promo grant (rewardJustGranted true exactly once).
Request body — application/json (required)
| Field | Type | Required | Notes |
|---|---|---|---|
step | "brand" | "upload" | "cleanup" | "model" | "tryon" | "organize" | "tokens" | yes | — |
{
"step": "brand"
}Responses
| Status | Meaning |
|---|---|
200 | Updated progress |
400 | BAD_BODY | UNKNOWN_STEP |
401 | No valid session |
200 returns:
{
"steps": {},
"completed": 0,
"total": 0,
"reward": {
"total": 0,
"granted": true
},
"rewardJustGranted": true
}Call it
curl -X POST "https://api.flam.fashion/api/toolkit/onboarding" \
-H "Authorization: Bearer $FLAM_API_KEY" \
-H "Content-Type: application/json" \
-d '{"step":"brand"}'