--- title: "Revise Shared Goal" method: POST path: "/goals/shared/{share_id}/revise" tags: ["goals"] --- # Revise Shared Goal `POST /goals/shared/{share_id}/revise` Start a conversation that revises this published goal, from the page alone. wonderland goals.md puts revising in the open on the page: while the live conversation is open the page just returns to it, and when it is gone — the cookie lost, the session expired — this is the path. The share payload is the whole input: a fresh conversation is seeded with the goal exactly as the page carries it, and nothing else survives, so the first coach turn works from the page without re-asking what it already says. Unsafe with all three browser signals, because it replaces whatever conversation this browser had — the same posture, rotation and response shape as ``POST /goals/session/reset``, so a client swallows it with the code it already has. The published goal itself is untouched: what this settles is a *new* goal, and publishing it is its own deliberate act. ## Path parameters - `share_id` string, required ## Response `200` Successful Response - GoalBrowserSessionResponse — What ``GET /goals/session`` hands the page back. Deliberately thinner than the Routes equivalent: the goals page has no session list to render and no route ancestry to carry, so it gets the two things it actually acts on — the CSRF token every turn must echo, and when the session stops being valid so it knows to bootstrap again. The session id rides along because it is what an operator matches a stored conversation on; it authorizes nothing on its own (the cookie does). - `session_id` string, required - `expires_at` string, date-time, required - `csrf_token` string, required ## Other responses - `422` — Validation Error --- [API](https://skmtc.dev/imperfect/apis/imperfect-api.md) · [All operations](https://skmtc.dev/imperfect/apis/imperfect-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/imperfect/imperfect-api/revisions/cc2293a44257/schema)