Skip to main content
Reset value learner state
Use the Adapt-1 value reset route for an intentional value-state boundary. It accepts the compatibility session_id within the authenticated Domain scope and is distinct from Domain /clear and /policy/reset. The bearer identity determines ownership. Verify your deployment’s post-reset state for observations, configuration, and models before incorporating reset into a workflow. The request tables below describe schema version 5. A default marked “Not declared” is absent from that schema; it does not mean null. Check /version at the API host root and confirm compatibility with your deployment.

Path, headers, and query

Send the hosted API key as Authorization: Bearer <ADAPT1_API_KEY>. The authenticated identity determines ownership; follow HTTP and contracts for the session placeholder. X-Neuroadapt-Session-Id is a compatibility header in schema version 5. It does not replace the hosted bearer identity.

JSON body contract

Content type: application/json. The HTTP request body is required. The following table describes its fields; linked schema names lead to the complete nested definitions on this page. When an array type also permits null, that alternative applies to the entire field, not to individual array items.

Request body

Schema: ValueRequest. Fields outside this object’s declared properties are rejected by the schema.

Responses

The validation error shape has an optional detail array. Each validation entry requires loc (an array of strings or integers), msg (string), and type (string); it can also include ctx (object) and input (any JSON value). Operational refusals can have their own error details. Verify the post-reset state returned by your deployment to confirm the operation’s effect on each part of value state. See reset and clear.