← Technical API reference

Backend resource · STATIC DECLARATIONS

Connect API reference · mansoq-onvif-console

Static source contract for Connect: 1 declared or inherited operation mappings, schema/field evidence and authorization/refusal references. Deployment and behavioral review remain explicit.

Static API contract — behavior review pending. Source baseline f6e9f05f76d4.

Enable JavaScript to inspect structured operation, parameter, schema and permission evidence. Download this reference and its evidence.

Declared route and availability

This resource is declared in mansoq-onvif-console at /api/connect. service-local decorator; application/router mount prefix and deployment base require verification A registered path and an indexed handler do not prove deployment availability, user permission or production readiness.

Operation map

Method Path Action Evidence
POST /api/connect connect service HTTP decorator

connect · POST

POST /api/connect — action connect. static function declaration extracted; request/runtime review pending.

parameter body: ConnectBody. Declared fields below; inherited fields are retained in the schema inventory.

Field Type Required Constraints
host str true No extra constraint extracted
port int false No extra constraint extracted
username str false No extra constraint extracted
password str false No extra constraint extracted

Authorization: no literal permission name was resolved in the bounded handler/helper traversal. Authentication, inherited policies, object/facility scoping and middleware still require review; this does not mean public access.

Declared refusal/error evidence: HTTPException (dynamic detail; inspect source).

Integration review checklist

Confirm the installed route and full schema; review authentication, organization/facility scoping, all accepted fields, value-state and date/time semantics, idempotency, pagination, response/exception branches and the allowed correction/reversal workflow. Test positive and negative cases with synthetic data. This source reference does not establish external certification or replace an illustrated user procedure.

Pinned source evidence

Links require access to the private source repository.