POST /api/track

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

What it does

Writes one funnel event for a store. The response distinguishes `counted` from `ignored`, so a client can tell a recorded event from a de-duplicated one instead of assuming every call landed.

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.
`product_id`	body	`string`	Required	The store the event belongs to.
`status`	body	`string`	Required	The funnel stage reached.

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 '{"product_id":"<string>","status":"<string>"}' \
  "https://flowfinds.ai/api/track"

const res = await fetch("https://flowfinds.ai/api/track", {
  method: "POST",
  credentials: "include",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "product_id": "<string>",
    "status": "<string>"
  }),
});
const data = await res.json();

import requests

s = requests.Session()
r = s.post("https://flowfinds.ai/api/track", json={
    "product_id": "<string>",
    "status": "<string>"
  })
data = r.json()

Recorded example

curl -s -b cookies.txt -c cookies.txt \
  -X POST -H 'Content-Type: application/json' \
  -d '{"product_id":"…","status":"cart"}' \
  "$FLOWFINDS_ORIGIN/api/track"

Responses

`200` — Always.

Field	Type	Description
`status`	`string`	`counted` or `ignored`.

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 — 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.

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