Confirm Extracted Goal
"This is right, hold me to it" (Mandate.dc.html L174, L587): the one click that both proposes and agrees a goal extracted from what Frederick said.
Two calls under the hood, not one -- goals.create_child_goal then goals.agree, the same two acts Admin's own goal editor makes for any other goal. The separation of "proposed" from "agreed" stays real in the audit trail even though one click triggers both here: it is only the plain POST /goals route (goals.propose) that is barred from doing both in a single call, because THAT route lets whoever proposes also be whoever signs off with no further act at all. Here the further act happens -- goals.agree -- it is just chained by the same already goals-write-gated principal in the same request, exactly mirroring "he proposes, he agrees" done by hand on two clicks instead of one.
Created UNMEASURED (no metric_key, no target) by default: nothing in a freeform sentence safely resolves to a wired feed, and a goal with no feed already has an honest home on this board -- the same "cannot be measured, here is why" card most of the goals on the live design wear.
⛔EXCEPT A GROWTH GOAL THAT NAMES A NUMBER AND A PERIOD (U2, 2026-09-25): "two county meetings a month" is created MEASURABLE, bound to marketing.meetings_booked with the stated target and window -- see _parse_measurable_meetings_goal for the rule and its scope.
Request
- Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
- URL: https://api.pigeonly.com/api/metrics/goals/confirm
- Auth: none declared
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.