Meta
3 Meta routes on the FLAM API: Swagger UI rendered over /openapi.json; Liveness; The merged OpenAPI document this API serves.
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 /docs
Swagger UI rendered over /openapi.json
Responses
| Status | Meaning |
|---|---|
200 | An HTML page |
Call it
curl -X GET "https://api.flam.fashion/docs" \
-H "Authorization: Bearer $FLAM_API_KEY"GET /health
Liveness
Unauthenticated. The readiness probe Tilt polls.
Responses
| Status | Meaning |
|---|---|
200 | The process is up |
200 returns:
{
"status": "ok",
"service": "api",
"uptime": 0
}Call it
curl -X GET "https://api.flam.fashion/health" \
-H "Authorization: Bearer $FLAM_API_KEY"GET /openapi.json
The merged OpenAPI document this API serves
The zod-openapi-generated half plus the hand-maintained half compiled from this file (bun run gen:openapi). /docs renders it. A route missing here is invisible to every generated client, typed SDK and MCP tool list.
Responses
| Status | Meaning |
|---|---|
200 | An OpenAPI 3.1 document |
200 returns:
{}Call it
curl -X GET "https://api.flam.fashion/openapi.json" \
-H "Authorization: Bearer $FLAM_API_KEY"