Consider exposing a minimal public API for integrations

Hello AntennaPod Team,

First off, thank you for AntennaPod. I’ve been using it specifically because it’s open-source, privacy-respecting, and not tied to a commercial ecosystem. That matters to me.

I’m writing to ask whether you would consider exposing a minimal, read-only API (or another supported integration mechanism) for AntennaPod.

There’s a growing ecosystem of tools like Home Assistant, self-hosted automation platforms, and AI-driven personal assistants that can benefit greatly from structured access to podcast metadata and playback state. Even very limited access would be extremely valuable.

Examples of what would already be useful:

  • Current episode metadata (podcast name, episode title)
  • Playback state (playing / paused)
  • Optional: listening progress or episode ID
  • Optional: subscription list (read-only)

This would enable things like:

  • Presence-aware automations (e.g., “what am I listening to”)
  • Logging or summarizing podcast content in AI tools
  • Accessibility and personal analytics
  • Smarter notifications and cross-device workflows

I completely understand and respect AntennaPod’s strong stance on privacy and avoiding unnecessary network services. Many users like me prefer that model. That’s why I’m not suggesting cloud services or tracking, just a local or opt-in API (for example: local REST endpoint, intent-based export, or documented content provider access).

Other apps in this space are increasingly exposing APIs, and AntennaPod’s philosophy puts it in a unique position to do this in a privacy-first, user-controlled way.

If this isn’t something you plan to support, I’d still appreciate knowing the rationale, or whether there’s an existing mechanism I may have overlooked.

Thanks again for all the work you do on the project.

Best regards,
Tom