Authentication
API keys, CLI tokens, and why there are no public topics.
Every request is authenticated. There are no public topics or unauthenticated channels — knowing a topic name grants nothing.
API keys
Keys look like std_live_…, belong to one project, and are sent as a
bearer token:
curl -H "Authorization: Bearer std_live_..." https://api.stdpush.com/v1/notify -d '{"title":"hi"}'- Stored hashed — we can't read them back, and neither can anyone who reads the database.
- Shown once at creation.
- Independently revocable — delivery stops the moment you revoke.
- Scoped:
notifications:writekeys can send but never read your history; addnotifications:readonly where needed.
CLI tokens
stdpush login pairs a machine through browser approval and stores a
std_cli_… token — a per-machine credential, listed and revocable under
Settings → Connected CLIs. Your password and browser session never
touch the terminal.
Key safety
Treat keys like passwords. If one leaks into a log or repo, revoke it in the dashboard — delivery stops immediately.