POST /api/product

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

What it does

Accepts a product the founder supplies rather than one the catalog found: name, description, price and images. Images are size-checked, and an oversized payload is refused with 413 rather than truncated. On success the store engine has a manifest and the response names its storefront and browsable path.

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.
`name`	body	`string`	Required	The product name. Refused as `invalid_name` when unusable.
`description`	body	`string`	Required	What the product is. Refused as `invalid_description` when unusable.
`price_usd`	body	`number`	Required	The asking price. Refused as `invalid_price` when unusable.
`images`	body	`string[]`	Required	Product images. Refused as `invalid_images`, or `images_too_large` with 413. A product with no real photo is not servable — the reveal is the product.
`product_id`	body	`string`	Optional	Publish under an existing identifier rather than minting one.

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' \
  -d '{"name":"<string>","description":"<string>","price_usd":"<number>","images":"<string[]>","product_id":"<string>"}' \
  "https://flowfinds.ai/api/product"

const res = await fetch("https://flowfinds.ai/api/product", {
  method: "POST",
  credentials: "include",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "name": "<string>",
    "description": "<string>",
    "price_usd": "<number>",
    "images": "<string[]>",
    "product_id": "<string>"
  }),
});
const data = await res.json();

import requests

s = requests.Session()
r = s.post("https://flowfinds.ai/api/product", json={
    "name": "<string>",
    "description": "<string>",
    "price_usd": "<number>",
    "images": "<string[]>",
    "product_id": "<string>"
  })
data = r.json()

Recorded example

curl -s -b cookies.txt -c cookies.txt \
  -X POST -H 'Content-Type: application/json' \
  -d '{"name":"…","description":"…","price_usd":39,"images":["data:image/…"]}' \
  "$FLOWFINDS_ORIGIN/api/product"

Responses

`200` — The product was published.

Field	Type	Description
`status`	`string`	`published`.
`product_id`	`string`	The identifier the product was published under.
`storefront`	`string`	The storefront path from the manifest.
`browsable_path`	`string`	The path that must resolve for the store to count as ready.

Errors

Status	Reason	When
`400`	—	A field failed validation. The body names the failing field.
`401`	—	The session has no account.
`409`	—	The identifier is already in use, or a build is already running for it.
`413`	`images_too_large`	The image payload exceeds the accepted size.
`500`	`generation_failed`	The store engine raised while building.

GET /api/offer — The researched offer for the session's product, or the refusal that says why there is none.
GET /api/dashboard — The verdict, the facts behind it, and where each figure came from.
GET /api/launch — The launch facts, each with whether it is true today.
POST /api/outcome — Declare what happened with a claimed product.
POST /api/product-launch — Drive the launch state machine for a product.
POST /api/presence — Record which screen the operator is on.

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