GET /api/store

What it does

`ready` is never asserted from the manifest alone: the store must exist on disk and its browsable path must resolve, or the status is whatever is actually true instead — a manifest is the generator grading itself. `not_started` and `failed` are kept apart, because a finished job with no manifest means a build happened and failed. `not_claimed` means no product resolved at all, on this surface as on every other. This GET records the `store_built` stage itself when it serves a ready store, because a store built by an earlier run is served ready here with no POST ever following it, and a count is only honest if every way of reaching a stage writes the same row.

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

Request

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

curl -s -b cookies.txt -c cookies.txt \
  "https://flowfinds.ai/api/store"

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

import requests

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

Recorded example

curl -s -b cookies.txt -c cookies.txt \
  "$FLOWFINDS_ORIGIN/api/store"

Responses

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.

Related

• POST /api/store — Start generating the storefront for the session's product.
• 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.