NzbDAV [Exposed!]

What is NzbDAV [Exposed!]?

NzbDAV [Exposed!] selectively opens the SABnzbd-compatible API endpoint of your NzbDAV instance to public access while leaving the WebDAV file-listing endpoint behind SSO. External tools can submit NZBs and check download status; nobody can browse your library.

Who needs this?

Anyone using external NZB-aware tools that need to submit jobs to NzbDAV:

• 🔍 NZBHydra2 (when running outside ElfHosted)
• 📺 AIOStreams and similar Stremio addons
• 🔌 Self-hosted Sonarr / Radarr / Prowlarr instances elsewhere
• 🤖 Custom automation scripts that POST NZBs to a SABnzbd-style API

Security requirements

The API requires the NzbDAV API key for authentication. Reset the default key before subscribing, then use the new key in your external tools’ SABnzbd-compatible configuration. The WebDAV endpoint that exposes your downloaded files remains protected by SSO — only the upload/status API is public.

Why ElfHosted?

Running NzbDAV at home means port-forwarding the SABnzbd API past your router and securing it with TLS yourself — and most home ISPs throttle inbound NZB POSTs that arrive in bursts. ElfHosted’s [Exposed!] gives you a stable, TLS-terminated public endpoint with datacentre-grade ingress so external tools can submit jobs reliably.

FAQ

Can someone download my files through the [Exposed!] API?
No — the API only accepts NZB submissions and reports status. File access still goes through the WebDAV endpoint, which remains SSO-protected.

What if my external tool only supports SABnzbd 2.x?
NzbDAV implements the canonical SABnzbd API surface that all major *arr apps and NZB clients target — compatibility should be transparent.