Learn

What is an API token?

A token is a credential with a narrower job than a password. It can be revoked on its own, limited in what it can do, and replaced without changing how you sign in.

What matters here

  • One token per tool or script
  • Shown once, stored hashed by the server
  • Revocable without touching your password
  • Carries your permissions, so treat it as secret
  • Long lived tokens need rotation

Why not use a password

A password proves who you are and usually unlocks everything. A token is issued for a purpose, can be scoped, and can be killed without locking you out of your own account.

Storage rules

The server should store only a hash, show the raw token once at creation, and never log it. If a service can show you the token again later, it is keeping more than it needs.

Handling them well

Keep tokens out of repositories and screenshots, give each integration its own token, and revoke anything you no longer use. A token in a public gist is a password in a public gist.

Frequently asked questions

Keep reading

Turn talk into a plan

Capture a thought in plain language and let Prysm Note shape it into tasks and a timeline.

Try Prysm Note

Disclaimer

This page is general information, not professional, legal, financial or medical advice. It describes common ways of working and how Prysm Note approaches them. Software changes over time, so details may differ from what you see in the product. Any product, company or brand names that appear are the property of their respective owners and are used only for identification. We do not claim any endorsement or affiliation. Where we compare approaches, we aim to describe each one honestly, including where a different approach may suit you better. Try the tools that matter to you and judge for yourself.