MANSOQ Frontend module · STATIC DECLARATIONS
Api client API reference · mansoq-web
1 client route/call declarations with path parameters, named payload/response types and source references. Exact server acceptance and permissions require the matched backend contract.
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.
Client contract scope
These 1 declarations come from repositories/platform/mansoq-web/src/lib/capabilities/api.ts. Client types and noAuth flags describe the caller; they do not authorize a server action. Dynamic paths and missing backend matches are retained as review work, not repaired into invented endpoints.
Operation map
| Client method | HTTP method | Path pattern | Resolution |
|---|---|---|---|
| capabilityApi.manifest | GET | /api/v1/tenant/capabilities/ |
literal |
capabilityApi.manifest
GET /api/v1/tenant/capabilities/. typed route object; literal. no exact statically resolved backend match in scanned contracts.
response type: CapabilityManifest. client-side declaration; not proof of accepted server payload.
CapabilityManifest declared fields:
| Field | Type | Required | Description |
|---|---|---|---|
| registryVersion | number | true | — |
| accessMode | "full" | "read_only" | "none" | true | — |
| capabilities | CapabilityManifestEntry[] | true | — |
| integrationsPending | string[] | true | — |
Operational limitation: request validation, permission checks, error statuses and irreversible side effects belong to the server implementation. An unmatched or computed client route requires contract review before use.
Pinned source evidence
Links require access to the private source repository.