Sign UpSign In
Wallabag API
Integrations & Sync

Save Articles from Your Phone

One of the most convenient ways to save articles for later reading is through your phone’s share menu. The Wallabag mobile apps for Android and iOS register as share targets on your device, so you can save a URL from any app — your browser, Twitter, Reddit, Mastodon, or anywhere else — by tapping “Share” and selecting Wallabag. Lion Reader implements the Wallabag API as a compatibility layer, so these apps work seamlessly with your Lion Reader account.

Compatible Apps

The official Wallabag apps work with Lion Reader out of the box:

  • wallabag — The official Wallabag app for Android, with share intent support and offline reading
  • wallabag 2 — The official Wallabag app for iOS, with share extension and offline reading

What You Can Do

The Wallabag API is scoped to saved articles in Lion Reader, matching the read-it-later interface that Wallabag apps expect. Through the app you can:

  • Save URLs — Share any URL to the Wallabag app to save it to Lion Reader
  • Browse saved articles — View your saved articles list with pagination and filtering
  • Read offline — The app caches articles for offline reading
  • Archive articles — Mark articles as read (archived) from the app
  • Star articles — Star your favorites for quick access
  • Search — Full-text search across your saved articles
  • Delete — Remove saved articles you no longer need

Setup

Setting up is straightforward. In the Wallabag app, go to Settings and enter:

  1. Server URL — Your Lion Reader URL with the Wallabag path (e.g., https://lionreader.com/api/wallabag)
  2. Client ID — wallabag
  3. Client Secret — wallabag
  4. Username — Your Lion Reader email address
  5. Password — Your Lion Reader password

Lion Reader also provides a QR code and a deep link in Settings > Integrations that pre-fill the server URL and your email address, so you only need to enter your password.

How It Works

The Wallabag API is implemented as a thin translation layer under /api/wallabag/. It follows the same pattern as the Google Reader API — each endpoint translates between the Wallabag wire format and Lion Reader’s existing services layer. This means saving an article through the Wallabag app uses the same saveArticle service as the web UI, browser extension, MCP server, and Discord bot.

Authentication uses OAuth 2.0 password grant, reusing Lion Reader’s existing token infrastructure. The client ID and secret are both wallabag — since Lion Reader validates credentials directly against user accounts, there is no need for per-client registration.

Entry IDs are mapped between Lion Reader’s UUIDv7 format and Wallabag’s integer IDs using a deterministic SHA-256 hash. This mapping is stable and reversible without storing any extra data.

Other Ways to Save

The Wallabag app is one of several ways to save articles in Lion Reader. You can also save via the browser extension, the bookmarklet, the PWA share target, the Discord bot, or the MCP server from AI assistants. All methods use the same underlying save service, so your saved articles end up in the same place regardless of how you captured them.