VEverdun
settings

Get Deepalert Default Threshold Impact

What changing the DeepAlert fleet default would move, counted by the server with the same resolver the camera reads and create-event use (never from a client-side tree). OWNER-ONLY, like the write. Carries the revision it counted against; the confirm dialog sends it as expected_revision. Literal path, no catch-all conflict with the / routes above.

get/settings/deepalert-default-confidence-threshold/impact

Request

  • Base URL
    https://api.verdun.ai (the document declares no server; this is the origin it was published from)
  • URL
    https://api.verdun.ai/settings/deepalert-default-confidence-threshold/impact
  • Auth
    HTTP bearer

Response

Successful Response

revisioninteger required

The fleet revision the counts were taken against. Send it as expected_revision; a 409 means refresh this resource.

valuenumber required

The fleet default in force at that revision.

ii_gated_following_fleetinteger required

ii_gated cameras with no override: they move with the fleet value.

ii_gated_invalid_overrideinteger required

ii_gated cameras whose stored override is unusable; they follow the fleet value (and need a deliberate repair in the camera form).

legacy_path_not_affectedinteger required

DeepAlert cameras on the legacy / II-off path. The fleet value does not affect them.

Example response

{
  "ii_gated_with_override": [
    {
      "value": 30,
      "cameras": 3
    }
  ]
}

Changes

No recorded changes to this operation across all 2 revisions of this API.