get_reclassify
const url = 'https://example.com/api/v1/reclassify';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/reclassify \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”The device nodes whose profile differs from the one the classification rules choose, with counts of locked and not-yet-identified nodes
What Nodes ▸ Reclassify shows.
object
Device nodes the rules were run for, whatever they chose. With proposals empty, 0 here
means nothing has been compared yet — not that every node matches.
Locked nodes the rules would move. Counted and never listed: a person fixed their profile. A lock is cleared from the node’s edit dialog.
Unlocked device nodes whose profile differs from the one the classification rules choose,
ordered by node name. At most 5,000 — total says how many there are.
One node the rules would move.
object
null ⇒ the node has no profile.
What the device last said it is — the input the rules ran on.
The vendor and model applying writes onto the node; null leaves the node’s own.
How many unlocked device nodes differ.
Device nodes the rules cannot be run for yet, because no sysObjectID is stored for them.
The poller reads it on its hourly identity probe, so a new or just-upgraded deployment fills
this in within the hour; a node that is not SNMP-polled never has one.
Examplegenerated
{ "identified": 1, "locked": 1, "proposals": [ { "current_profile_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "current_profile_name": "example", "model": "example", "node_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "node_name": "example", "rule": { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "priority": 1, "sysdescr_regex": "example", "sysobjectid_prefix": "example" }, "suggested_profile_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "suggested_profile_name": "example", "sys_descr": "example", "sys_object_id": "example", "vendor": "example" } ], "total": 1, "unidentified": 1}No valid bearer token
The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI
document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies
undescribed — a client that has to guess the failure shape ends up parsing the success shape and
reading undefined.
object
object
Stable machine-readable code. Clients branch on this, never on the message.
Operator-facing sentence. Safe to display; never carries an internal error’s own text.
Examplegenerated
{ "error": { "code": "example", "message": "example" }}Role lacks ManageConfig
The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI
document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies
undescribed — a client that has to guess the failure shape ends up parsing the success shape and
reading undefined.
object
object
Stable machine-readable code. Clients branch on this, never on the message.
Operator-facing sentence. Safe to display; never carries an internal error’s own text.
Examplegenerated
{ "error": { "code": "example", "message": "example" }}This deployment has no write side (skeleton mode)
The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI
document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies
undescribed — a client that has to guess the failure shape ends up parsing the success shape and
reading undefined.
object
object
Stable machine-readable code. Clients branch on this, never on the message.
Operator-facing sentence. Safe to display; never carries an internal error’s own text.
Examplegenerated
{ "error": { "code": "example", "message": "example" }}