POST /api/fix/event

Request	`POST /api/fix/event`
Authentication	Session cookie optional
Handler	`backend/fixtool.py`

What it does

One handler serves `/api/fix/event` and `/api/fix/feedback`. Feedback that asks for no follow-up is acknowledged as such — the response says the follow-up is suppressed rather than silently dropping it.

Authentication

Session cookie optional. The endpoint answers with or without ff_session, but the body is scoped to the session when one is present.

Parameters

Parameter	In	Type	Required	Description
`token`	body	`string`	Required	The run the event belongs to.
`event`	body	`string`	Required	The event name. Refused as `unknown_event` when it is not one the tool defines.
`detail`	body	`string`	Optional	Free text accompanying the event.

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 '{"token":"<string>","event":"<string>","detail":"<string>"}' \
  "https://flowfinds.ai/api/fix/event"

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

import requests

s = requests.Session()
r = s.post("https://flowfinds.ai/api/fix/event", json={
    "token": "<string>",
    "event": "<string>",
    "detail": "<string>"
  })
data = r.json()

Recorded example

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

Responses

`200` — Recorded.

Field	Type	Description
`status`	`string`	`recorded`.

`200` — Recorded with follow-up suppressed.

Field	Type	Description
`status`	`string`	`recorded`.
`explanation`	`string`	'Recorded. Follow-up about this report is suppressed.'

Errors

Status	Reason	When
`400`	`unknown_event`	The event name is not defined.
`404`	—	No run carries that token.

POST /api/fix — Submit a store URL for repair.
GET /api/fix/mine — The state of a Fix run, or this account's Fix subscriptions.
POST /api/fix/adopt — Attach a Fix run to this session.

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