Skip to main content

​
Overview

The timeback credentials command manages local API credentials for the Timeback and MasteryTrack providers. Credentials are stored as JSON in ~/.timeback/credentials.json; the CLI creates the directory with mode 0700 and writes the file with mode 0600.
If you’re just getting started, timeback init will automatically prompt for credentials when needed. Use timeback credentials when you need explicit control over credential management.

​
Commands

​
add

Add credentials interactively:
The default provider is timeback. Choose one or more environments, then enter the client ID, client secret, and optional email for each environment. The email is used to look up your OneRoster profile. API and token URLs are resolved from the provider and environment. For MasteryTrack, select its provider explicitly:
The MasteryTrack wizard collects an API key and registered email for each selected environment.

​
email

Add or update the email associated with your saved Timeback credentials:

​
list

List stored credentials:

​
remove

Remove stored credentials:

​
Credential Priority

The CLI looks for credentials in this order:
  1. Environment variables
  2. Stored credentials
For Timeback, use TIMEBACK_API_CLIENT_ID and TIMEBACK_API_CLIENT_SECRET. The legacy TIMEBACK_CLIENT_ID and TIMEBACK_CLIENT_SECRET aliases are also accepted. For MasteryTrack, use TIMEBACK_MASTERYTRACK_API_KEY and TIMEBACK_MASTERYTRACK_EMAIL; the legacy MASTERYTRACK_API_KEY and MASTERYTRACK_EMAIL names remain supported.

​
Next Steps

CLI: API

Use credentials to query APIs

CLI: Resources

Manage course configurations