POST /api/store

Request	`POST /api/store`
Authentication	Session cookie required
Handler	`backend/server.py`

What it does

Kicks off a build. Poll `GET /api/store` for the stage. The engine holds a job lock per product, so a second POST while a build is running does not start a second build.

Authentication

Session cookie required. Send the ff_session cookie. Without one the engine treats the caller as a new visitor with no holds and no claims, and returns a new cookie to use from then on.

Parameters

Parameter	In	Type	Required	Description
`ff_session`	cookie	`string`	Optional	The session identifier. Omit it on the first call and store the value the response sets; every later call must send the same one or the engine treats the caller as a new visitor with no holds and no claims.

Request

The cookie jar carries the session between calls. Angle-bracketed values are the parameter types from the table above.

cURLJavaScriptPython

curl -s -b cookies.txt -c cookies.txt \
  -X POST -H 'Content-Type: application/json' \
  "https://flowfinds.ai/api/store"

const res = await fetch("https://flowfinds.ai/api/store", {
  method: "POST",
  credentials: "include",
});
const data = await res.json();

import requests

s = requests.Session()
r = s.post("https://flowfinds.ai/api/store")
data = r.json()

Recorded example

curl -s -b cookies.txt -c cookies.txt \
  -X POST -H 'Content-Type: application/json' \
  -d '{}' \
  "$FLOWFINDS_ORIGIN/api/store"

Responses

`200` — A build was started, or one is already running — the response carries the job's stage.

`200` — No product is resolved.

Field	Type	Description
`status`	`string`	`not_claimed`.
`explanation`	`string`	The store copy.

Errors

This endpoint has no failure path of its own. An uncaught exception anywhere in the engine is still returned as structured JSON by the shared guard.

GET /api/store — The state of the session's storefront.
POST /api/store/publish — Verify and publish the storefront, regenerating it if verification demands.
POST /api/intent — Ask the engine what it would change on a surface, and why.
POST /api/intent/apply — Apply a proposed intent, regenerating the store.
POST /api/intent/order — Override the section the storefront leads with.
POST /api/intent/revert — Undo the last applied intent.
POST /api/ai/edit — Edit the storefront in natural language.
GET /api/editor/ — Read editor state and store metrics.

Back to the API reference index, or read the cookbook for recipes that compose this endpoint with others.