Documentation
POST /api/editor/publish
Publish the editor's draft.
| Request | POST /api/editor/publish |
|---|---|
| Authentication | Session cookie required |
| Handler | backend/editor10x.py |
What it does
Publishes what the editor has staged. When the response comes back 200 with `status: "ready"`, the engine records the publication itself rather than relying on the client to report it.
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.
curl -s -b cookies.txt -c cookies.txt \
-X POST -H 'Content-Type: application/json' \
"https://flowfinds.ai/api/editor/publish"const res = await fetch("https://flowfinds.ai/api/editor/publish", {
method: "POST",
credentials: "include",
});
const data = await res.json();import requests
s = requests.Session()
r = s.post("https://flowfinds.ai/api/editor/publish")
data = r.json()Recorded example
curl -s -b cookies.txt -c cookies.txt \
-X POST -H 'Content-Type: application/json' \
-d '{}' \
"$FLOWFINDS_ORIGIN/api/editor/publish"Responses
200 — The draft was published. `status` is `ready` on success.
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
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.