Manage your link in bio from the terminal (CLI guide)
Manage your link in bio from the terminal
You can manage your isall.me page entirely from the command line using the isall.me CLI. It's an npm package called isallme, so you run it with npx isallme, point it at your API token, and edit your links, theme, and profile without ever opening the dashboard.
This is for people who'd rather stay in the terminal, and for scripting page updates into your own tools.
Here's how to set it up and what it can do. This post is part of our developer cluster, and the full reference lives at the hub: https://isall.me/developers.
Why a CLI for a link in bio?
Because some updates are faster typed than clicked, and some updates you want to automate.
A few real cases:
- You ship a new release and want to update the top link as part of your deploy script.
- You manage several pages and want to update them all from one place.
- You just prefer the keyboard and don't want to leave your shell.
The CLI turns your page into something you can script. Anything you can do in the dashboard, you can wire into a command.
What you need
Two things:
- Node.js installed, which gives you npx. If you can run node --version, you're set.
- An API token starting with isam_, minted in your dashboard. Developer access is a Pro feature, and Pro is 24 dollars per year with a 0 percent fee on tips and sales.
You don't install the CLI globally unless you want to. npx isallme fetches and runs the latest version each time.
Step 1 to 5: get running
The whole setup, start to finish.
-
Mint your token. In the isall.me dashboard, open the Developer tab and create a new token. You'll get a string starting with isam_. Pick read-only if you only want to read analytics, or full access if you want to edit your page. Copy it right away, since the full value is shown once.
-
Give the CLI your token. The CLI reads your token from an environment variable called ISALLME_TOKEN. Export it in your shell so the CLI can find it. In bash or zsh you set ISALLME_TOKEN to your isam_ value. To make it stick, add that export line to your shell profile.
-
Confirm it works. Run npx isallme whoami. If the token is good, it prints your account and page. If it errors, check that the token is set and hasn't been revoked.
-
List what's on your page. Run npx isallme links list to see your current links. This is the safest first real command and confirms the CLI is reading your live page.
-
Make your first change. Add a link with a command like npx isallme links add, passing the title and URL. Run the list command again to confirm it landed. That's the full loop: read, change, verify.
Once whoami works, everything else is just more commands.
Common commands
The exact flags are in the docs, but the shape of it looks like this:
- npx isallme whoami shows the account tied to your token.
- npx isallme links list prints your current links.
- npx isallme links add adds a new link with a title and URL.
- npx isallme links remove takes down a link.
- npx isallme theme set switches your page theme.
- npx isallme analytics pulls your click numbers.
Because it's a normal command-line tool, you can pipe output, save it to a file, or drop any of these into a shell script.
Scripting and automation
This is where the CLI earns its place.
Since every action is a command, you can put those commands in a script and run them on a schedule. A cron job or a GitHub Action can call the CLI to update your page without you touching anything.
An honest note on what that means: there's no built-in one-click auto-poster. What you get is the tools, and you wire your own script or agent to them. That's a feature, not a limitation, because you control exactly what runs and when.
A simple pattern:
- Write a small script that calls npx isallme links add with your latest release URL.
- Store your ISALLME_TOKEN as a secret in your CI system, never in the script itself.
- Trigger the script from a GitHub Action on release, or from cron nightly.
If you want the deeper version of this, we cover full automation setups in /blog/automate-link-in-bio, and the raw HTTP layer under the CLI in /blog/link-in-bio-api.
CLI vs the API vs MCP
Same account, same token, three ways in. Pick by taste:
- The CLI is best for terminal work and shell scripts.
- The REST API at https://isall.me/api/v1 is best when you're calling from your own code in any language.
- The MCP server is best when you want an AI assistant editing your page in plain language.
They all read the same isam_ token, so you can mix them. Manage by hand in the terminal today, script it tomorrow.
Keeping your token safe
The token is the keys to your page, so treat it like a password.
- Never commit it to a repo. Use an environment variable or a secret store.
- Use a read-only token for anything that only needs to read, like analytics scripts.
- If a token leaks, revoke it in the Developer tab and mint a new one. Old tokens stop working immediately.
FAQ
Do I need to install anything?
Just Node.js. The CLI itself runs through npx isallme, which fetches it on the fly. You can install it globally if you run it constantly, but you don't have to.
Is the CLI free?
The npm package is free to download. To do anything with it you need an isam_ token, and tokens are a Pro feature. So you need isall.me Pro, which is 24 dollars a year.
Can I use the CLI in a CI pipeline?
Yes. Set ISALLME_TOKEN as a secret in your CI environment and call the CLI from your workflow. That's the standard way to update your page automatically on a release or a schedule.
What's the difference between the CLI and the API?
The CLI is a friendly wrapper you run in a terminal or script. The API is the raw HTTP endpoint the CLI talks to. Use the CLI for convenience, and go straight to the API when you're building something custom in code.
Claim your link and mint a token
Ready to run your page from the terminal? You'll need a page and a token first.
Create your link at https://isall.me/signup, upgrade to Pro, then open the Developer tab to mint your isam_ token. Export it as ISALLME_TOKEN, run npx isallme whoami to confirm, and you're managing your bio from the command line.
Full developer docs live at https://isall.me/developers.
Free to start. Pro is $24 a year, not $24 a month.
Claim your link, free