Credentials and tokens

Every upload needs a credential. The CLI takes the first one it finds:

1. --token <token>
2. the EASYTRACE_TOKEN environment variable
3. the easytrace login session stored on this machine for the API URL in use — together with the project from --project or project in easytrace.config.json

Nothing found:

EasyTrace: not signed in — run `easytrace login`, or set EASYTRACE_TOKEN in CI.

The tests still run; nothing is uploaded.

Project tokens

For CI and other shared machines.

• Created in the dashboard: project → Setup → Create token. The full token (et_proj_…) is shown once; the list only keeps its first characters.
• A token can upload to its project only, and do nothing else.
• Name tokens after where they are used (GitHub Actions, CircleCI) and revoke the one you no longer need. A revoked token is rejected immediately (token rejected — results were not uploaded).
• Store it as a secret. Never commit it — easytrace.config.json is meant to be public within the repository.

CLI sessions (easytrace login)

For developer machines. See Uploading from your machine.

	Project token	CLI session
Created	Dashboard, by a project member	easytrace login + Authorize in the browser
Uploads to	One project	Any project of your organizations (project in the config)
Runs show as	CI (or Local when no CI is detected)	Local, uploaded by you
Lifetime	Until revoked	90 days after last use, or until revoked
Other access	None	Read your user, organizations and projects (for whoami / init)
Revoke	Project → Setup	CLI sessions page, or easytrace logout

API URL

Credentials are stored per API URL, so the same machine can be signed in to the hosted EasyTrace and a self-hosted one. The URL comes from --api-url, then EASYTRACE_API_URL, then apiUrl in the config, then https://api.easytrace.dev.