Managing project keys
Create keys on the project’s API Keys page in the Moss Portal. New projects start with no key.- Shown once. A key is displayed only at creation. Store it in a secret manager right away. If you lose it, create a new one.
- Rotate with overlap. Create a new key, move your clients to it, then delete the old one. A project can hold several keys at once, so nothing goes down during the switch.
- Delete revokes. Deleting a key blocks new tokens right away. Tokens already issued with it stop working within about 20 seconds.
Session authentication
Project credentials are validated when a session is opened:client.session(...) raises if they’re invalid. For long-lived sessions, tokens are cached and auto-refreshed, so you stay authenticated without re-supplying credentials. See Sessions.