Refresh guided checklist signals on demand

post/api/usermanagement/v1/users/{userId}/properties/guided-checklist/refresh

Re-evaluates server-knowable signals (CUS-515) for any non-completed step in the user's guided checklist and persists any step transitions to COMPLETED in a single transaction. Caller invokes this when they expect new state — typically after returning from a downstream action (created a wallet, set a policy, etc.). Membership is validated up front; callers without an active role in the organization receive 403.

Path Parameters

  • userIdstringRequired
    External user ID

Query Parameters

  • orgIdstringRequired
    Organization ID. Multi-tenancy is validated against the caller.
  • enterpriseIdstringRequired
    Enterprise ID. Must belong to `orgId`. Scopes signal lookups.

200 Response

userId string required
External user ID
guidedChecklist object
track string required
Guided checklist track
Allowed values: A B
roles array[string]
The user's roles in the requested organization, resolved at read time from role-user membership. Used by the server to filter visible steps. Values written via PUT/PATCH are stored but overwritten on GET by the resolved values, so this field always reflects the user's current roles in the org rather than a stored snapshot.
productInterests array[string]
User product interests
steps array[object]
Checklist steps
computedAt string <date-time>required
When the checklist was last computed
completedAt string <date-time>
When the checklist was completed
dismissedAt string <date-time>
When the checklist was dismissed
createdDate string <date-time>required
When the record was created
modifiedDate string <date-time>required
When the record was last modified