# Wrapper Gaps and Direct API Candidates Several Synology domains look operationally rich by namespace, but the current Python wrapper surfaces only a thin read layer. Those gaps are not dead ends; they are likely the best candidates for direct DSM API work once the wrapper-level research is exhausted.[^api-index] ## 1. Synology Drive Admin Drive Admin namespaces exist for config, settings, shares, profiles, logging, connection state, and indexing, yet the standout action exposed in the wrapper is essentially just `index_pause`.[^drive-admin] This makes Drive a strong candidate for deeper direct DSM API work around team-folder management, service settings, migration controls, and quota/policy changes. ## 2. KeyManager and encrypted-share key handling The upstream docs tracker marks both `KeyManagerStore` and `KeyManagerAutoKey` as `not_started`, and current wrapper guidance is not sufficient for real encryption-key lifecycle automation.[^docs-status][^core-share] That makes key-management flows a high-value direct DSM target for anyone trying to automate encrypted shared-folder operations safely. ## 3. Log Center and notification plumbing Log Center surfaces receive rules, storage settings, client forwarding state, and history, but the wrapper is read-only here.[^log-center] Because these are clearly administrative concerns, this is a good research path for discovering whether direct `SYNO.LogCenter.*` and `SYNO.Core.Notification.*` calls can unlock real log-routing and notification-policy automation beyond mere inspection.[^log-center][^core-sysinfo] ## 4. OAuth client administration The wrapper exposes client, token, and log listings, but no client CRUD or token revocation.[^oauth] That suggests the wrapper is acting as an audit surface while the underlying DSM APIs may still support actual client-registration management. ## 5. Note Station and app domains with one-way coverage Note Station is effectively read-only in the wrapper despite obviously CRUD-shaped domains like notebooks, notes, tags, and todos.[^notestation] This probably matters less for system administration than Docker or Drive, but it is still evidence that the wrapper often maps only the read half of a Synology namespace family. ## 6. Network/security namespaces that sound stronger than they are VPN, DHCP, Security Advisor, QuickConnect, DDNS, port forwarding, and firewall-related namespaces show up in the wrapper's class inventory, but the currently documented methods are mostly getters.[^vpn][^dhcp][^security-advisor][^core-sysinfo] This means future research should be careful not to over-credit these areas just because the namespace names look powerful. They are promising only if direct DSM requests or source inspection confirm mutating methods. ## Practical implication The project should keep two clearly separated tracks: 1. **Wrapper-confirmed control** — what is already usable now. 2. **Direct DSM candidates** — what likely exists below the wrapper and deserves targeted reverse engineering. Docker and Virtualization no longer belong in this gap note; they now sit in the "implemented but partially or poorly documented" bucket documented in [[implementation-vs-doc-status]]. That separation is crucial to answering the user's real question honestly.[^docs-status][^docker-source][^virtualization] [^api-index]: Synology API class index: https://n4s4.github.io/synology-api/docs/apis [^docs-status]: Upstream documentation status tracker: https://github.com/N4S4/synology-api/blob/master/docs_status.yaml [^docker-source]: Docker source entrypoint: https://github.com/N4S4/synology-api/blob/master/synology_api/docker_api.py [^drive-admin]: Drive Admin Console docs: https://n4s4.github.io/synology-api/docs/apis/classes/drive_admin_console [^core-share]: Core Share docs: https://n4s4.github.io/synology-api/docs/apis/classes/core_share [^log-center]: Log Center docs: https://n4s4.github.io/synology-api/docs/apis/classes/log_center [^core-sysinfo]: Core SysInfo docs: https://n4s4.github.io/synology-api/docs/apis/classes/core_sys_info [^oauth]: OAuth docs: https://n4s4.github.io/synology-api/docs/apis/classes/oauth [^notestation]: Note Station docs: https://n4s4.github.io/synology-api/docs/apis/classes/notestation [^vpn]: VPN docs: https://n4s4.github.io/synology-api/docs/apis/classes/vpn [^dhcp]: DHCP Server docs: https://n4s4.github.io/synology-api/docs/apis/classes/dhcp_server [^security-advisor]: Security Advisor docs: https://n4s4.github.io/synology-api/docs/apis/classes/security_advisor [^virtualization]: Virtualization source entrypoint: https://github.com/N4S4/synology-api/blob/master/synology_api/virtualization.py