Automate capture with API tokens
Mint a personal access token and anything that can make an HTTP request can save bookmarks into your workspace — the iOS share sheet, scripts, or your own tools.
In Settings → API tokens you can mint a personal access token — a dxi_-prefixed secret shown once and revocable anytime. A token authenticates exactly one thing: saving bookmarks. That narrow scope is deliberate — a token in a phone shortcut or a script can add to your library, but it can’t read, change or delete anything.
The flagship use is the iPhone share sheet: an iOS Shortcut holding your token turns “share → Dexi” into a save from Safari, Twitter, your RSS reader — any app that can share a link. But anything that speaks HTTP works: a shell alias, a step in an automation platform, a cron job.
Why it matters
Capture tools live or die on being available at the moment of encounter, and a lot of encounters happen on the phone or inside other tools. Tokens extend one-click saving beyond the browser extension to effectively everywhere.
The write-only scope changes the risk calculus of automating. You can put a token in an iOS Shortcut, a coworker-visible script or a third-party automation with a clear worst case: if it leaks, someone could add bookmarks to your account until you revoke it — not read a decade of private notes.
Who gets the most out of it
- Mobile-first readers — Most discovery happens on the phone; the share sheet makes the phone a first-class capture device.
- Developers — A curl one-liner or shell alias saves links from the terminal without touching a browser.
- Automation builders — Zapier-style workflows and scripts can route links from other services into your library.
- Security-conscious users — Hashed at rest, shown once, single-purpose, revocable per token — automation without handing out your password.
Example: A developer’s phone-to-workspace pipeline
You read mostly on your phone — Mastodon, newsletters, a feed reader — and links you mean to keep die in a self-messaged chat thread.
- In Dexi’s Settings → API tokens you mint a token named “iPhone shortcut” and copy it — it’s shown this once.
- You build a two-step iOS Shortcut: receive a URL from the share sheet, then POST it to Dexi’s bookmark-save endpoint with the token in the header. Add it to the share sheet and you’re done.
- From then on, saving from any app is share → Dexi. The page lands in your workspace with its title, ready to tag next time you’re at a desk.
- Months later the shortcut misbehaves after an iOS update; you revoke just that token in Settings — your password, sessions and other tokens are untouched.
Try it in your own workspace — free, no credit card required.
Get started