Does Marqly have an API?

No. Marqly doesn’t have a public API today. There’s no documented endpoint for creating saves, reading your library, or wiring Marqly into automation tools, and no self-hosted option either. If an API matters for your workflow, email support@marqly.com and describe what you’d build with it — concrete use cases from real users are exactly what shapes priorities.

Why tell us anyway

“API” means something different to everyone: push saves in from a script, pull your library into another tool, trigger automations when something is saved. Which of those ships first — if any — depends on which ones people actually ask for. A two-line email with your use case is more useful than you’d think. How to reach us has the details, but the short version is support@marqly.com.

Getting data in without an API

For most “I want to get my stuff into Marqly” cases, an API isn’t actually required. Marqly imports Pocket export files, Raindrop.io collections, and the standard bookmark HTML file that Chrome, Firefox, Edge, and Safari all export. Day to day, the browser extension is the capture path: one-click save, save-with-tags, and a tab saver that captures every open tab at once.

Getting data out

Your saves aren’t locked in — see can I export my data for what leaving with your library looks like.

Will there be a public API later?

Maybe — but we don’t promise features or dates we might not hit, and an API commitment made in a FAQ is exactly that kind of promise. The honest status lives on what’s on the roadmap: Marqly is actively developed, updates land on @getmarqly on X first, and if a public API ships, that’s where you’ll hear about it.