autopilot
Read Setup Plan
The caller's saved Setup Plan intake, or 204 when they have not made one.
The same 204 contract as GET /profile, and for the same reason: the route exists and the caller is entitled to it, there is simply nothing stored yet — and 404 is already this router's "the feature is off" signal, so reusing it here would be ambiguous.
What comes back is the inputs, not a plan. POST /api/plan turns them into one deterministically, and that is where the rendering belongs: a plan stored here would go on disagreeing with a recomputed one after any change to the tax engine, with nothing to say which of the two the user had read.
get/api/autopilot/setup-plan
Request
- Base URL: https://api.taxcompass.it (the document declares no server; this is the origin it was published from)
- URL: https://api.taxcompass.it/api/autopilot/setup-plan
- Auth: HTTP bearer
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.