Teams, activity and API
Commands for team management, the activity feed, API tokens, and direct API access.
Teams
yofix teams listyofix teams switch acmeyofix teams usageyofix teams usage --period previous| Command | Argument / flags |
|---|---|
teams list | List teams you belong to |
teams switch <teamSlug> | Set the active team (alias of top-level switch) |
teams usage | --period <current|previous> |
yofix activity
Show recent activity. Team-scoped by default; --project scopes to the
linked project.
yofix activityyofix activity --type deploy --branch main --limit 20yofix activity --project| Flag | Default | Description |
|---|---|---|
--branch <branch> | all | Filter by git branch |
--type <type> | all | Filter by kind: deploy or vrt |
--limit <n> | 20 | Maximum rows |
--project | team scope | Scope to the linked project instead of the whole team |
Tokens
Manage team API tokens. Every token acts within your team at the role you
allow, and by default reaches only the linked project. The secret is shown
once at creation. Token management needs a session login (yofix login), not
a token: a credential can never mint or revoke credentials.
yofix tokens listyofix tokens create "CI deploy" --expires 2026-12-31T00:00:00Zyofix tokens create "Agent access" --role viewer --all-projectsyofix tokens revoke <apiKeyId>| Command | Argument / flags |
|---|---|
tokens list | List the team’s API tokens with role and scope |
tokens create <label> | --role <role> (viewer, developer, admin; default developer), --all-projects (reach every team project instead of only the linked one), --expires <iso> (optional ISO-8601 expiry) |
tokens revoke <apiKeyId> | Revoke an API token |
API
Call the YoFix API directly, with auth and team headers already wired. See Agents, JSON and MCP.
yofix api listyofix api list --tag deploymentsyofix api call GET /v1/projectsyofix api call POST /v1/projects/:id/deployments --data '{"target":"preview"}'yofix api curl /v1/projects| Command | Argument / flags |
|---|---|
api list | --tag <tag> — list endpoints from the OpenAPI spec |
api call <method> <path> | --data <json> — call any endpoint |
api curl <path> | --method <method>, --data <json> — print the curl command (does not run it) |