Authentication

Create an account with an email address and a password of at least 8 characters, or continue with Google. When you sign up with email you also provide your country, a phone number, and optionally your organization, and you accept the Terms of Service and Privacy Policy. Google sign-ups complete the same details in onboarding. Sessions in the console last 7 days.

clockingcloud login

1. The CLI opens clockingcloud.com with a one-time authorization request.
2. Sign in if needed and approve the request.
3. The CLI stores a credential in ~/.config/clockingcloud/credentials.json and prints your account email.

Use --no-browser to print the URL instead of opening it, for example inside a container.

clockingcloud login --device

The CLI prints a short code and a URL. Open the URL on any device, enter the code, and approve. The CLI completes when you do. The code expires after 10 minutes.

clockingcloud api-key create --name github-actions --expires 90d

The secret begins with cc_live_ and is displayed once. ClockingCloud stores only a hash, so a lost key cannot be recovered. Create a new one and revoke the old one.

export CLOCKINGCLOUD_API_KEY=cc_live_xxxxxxxxxxxxxxxx
clockingcloud ls

curl https://www.clockingcloud.com/v1/instances \
  -H "Authorization: Bearer $CLOCKINGCLOUD_API_KEY"

1. CLOCKINGCLOUD_API_KEY in the environment.
2. The credential stored by clockingcloud login (or clockingcloud login --with-api-key).

Run clockingcloud whoami to see which account the CLI is acting as.

clockingcloud api-key ls
clockingcloud api-key create --name github-actions-2 --expires 90d
clockingcloud api-key rm key_8f3a1c
clockingcloud logout

Revocation takes effect immediately for new requests. clockingcloud logout removes the local credential and ends the CLI session but does not revoke API keys.