admin-onboarding

Get Draft Detail

One person's wizard state, in the wizard's own words (admin surface P5).

GET /onboarding/draft is self-keyed by design, so before this an admin could see that somebody was stuck and not what on — which made the funnel unactionable.

The checklist is render_progress_block verbatim, deliberately: an admin view that paraphrased it would give the operator different words from the ones the customer is reading in their own help chat, and the support call becomes two people describing different screens.

uncomputed names the context keys the server cannot derive from the stored draft blob — the wizard's help chat receives a context the browser assembles, and three of its keys need gating logic that would have to be duplicated (and would then drift). Those steps read vaguer here than on the user's own rail; the field is sent so the UI can say so rather than presenting a partial checklist as complete.

get/admin/onboarding/{user_id}

Request

  • Base URL: https://app.zeno-works.ch (the document declares no server; this is the origin it was published from)
  • URL: https://app.zeno-works.ch/admin/onboarding/{user_id}
  • Auth: none declared

Path parameters

user_idstring required

Headers

authorizationstring nullable

Cookies

access_tokenstring nullable

Response

Successful Response

user_idstring required
emailstring required
current_stepstring required
updated_atstring date-time required
step_entered_atstring date-time nullable required
progress_blockstring required
next_actionstring required
blocker_codesstring[] required
blockers_knownboolean required
blockers_recorded_atstring date-time nullable required
uncomputedstring[] required

Changes

No recorded changes to this operation across all 1 revision of this API.