Coder · Controlled Vocabulary
Coder API Vocabulary
Core terminology and concepts used across the Coder REST API v2 for managing cloud development environments (CDEs), workspace lifecycle, templates, users, organizations, and workspace agents.
21 Terms
Updated
Coder Vocabulary is a controlled vocabulary published by Coder on the APIs.io network, defining 21 terms.
Defined terms include workspace, template, template-version, workspace-build, and workspace-agent.
A controlled vocabulary pins the words an API’s schemas, parameters and documentation use to one agreed definition each — the shared language a human or an agent needs to read the API the same way its authors do.
Terms
workspace
An isolated cloud development environment provisioned from a template. Each workspace has a lifecycle (start, stop, delete) and runs one or more workspace agents that provide terminal, IDE, and port-forwarding access.
template
A versioned blueprint for creating workspaces, defined using Terraform and stored as a ZIP archive. Templates specify infrastructure resources, parameters, and lifecycle scripts. Organizations manage their own template catalogs.
template-version
A specific immutable revision of a template. New versions are created by uploading a new Terraform bundle. Workspaces can be updated to newer template versions.
workspace-build
A record of a provisioning job applied to a workspace for a specific transition (start, stop, delete). Each build references a template version and contains the job status, resources, and deadline.
workspace-agent
A process running inside a workspace resource that handles terminal (PTY) access, app health checks, port sharing, log streaming, and WireGuard/Tailnet coordination. Agents authenticate via instance identity tokens (AWS/Azure/GCP) or pre-shared keys.
workspace-app
A web application or service exposed by a workspace agent, accessible through the Coder dashboard or a subdomain proxy. Apps have health check URLs, sharing policies, and open/external URL behaviors.
organization
A tenant grouping of users, templates, and workspaces within a Coder deployment. Enterprise deployments support multiple organizations with separate RBAC policies, IdP sync, and provisioner keys.
user
A Coder account identified by username and email. Users authenticate via password, GitHub OAuth, OIDC, or API tokens. Each user belongs to one or more organizations and holds roles that govern permissions.
api-key
A long-lived or session-scoped authentication credential passed in the Coder-Session-Token HTTP header. API keys have optional expiry, lifetime limits, and token names for management.
provisioner-job
An asynchronous task executed by a provisioner daemon (Terraform) to apply, plan, or destroy workspace infrastructure. Jobs have statuses (pending, running, succeeded, failed, canceled) and stream logs.
audit-log
An immutable record of a user or system action (create, write, delete) on a Coder resource such as a workspace, template, user, or organization. Audit logs include actor identity, IP address, user-agent, and a diff of changed fields.
group
A named collection of users within an organization used for template ACL grants and RBAC assignments. Groups can be synced from an external IdP via OIDC claims.
role
A named set of permissions scoped to a site (global) or organization. Built-in roles include owner, template-admin, user-admin, auditor, and member. Enterprise deployments support custom roles with fine-grained permission sets.
wireguard
The encrypted peer-to-peer VPN protocol used by the Coder Tailnet to connect developer clients directly to workspace agents without exposing SSH ports. Each agent receives a WireGuard public key registered on the coordination server.
coder-session-token
The HTTP header name (Coder-Session-Token) used to pass API key credentials to the Coder API. All authenticated endpoints require this header unless the endpoint is public.
dormancy
A lifecycle state where a workspace is automatically stopped after a configurable period of inactivity (time_til_dormant_ms). Dormant workspaces can be auto-deleted after a further period (time_til_dormant_autodelete_ms).
autostart
A cron-based schedule that automatically starts a stopped workspace at a specified time. Encoded as a cron expression with an optional CRON_TZ timezone prefix.
autostop
A TTL-based or template-enforced policy that automatically stops a running workspace after a configurable idle period or at week-end boundaries.
deployment
A running Coder server instance (coderd) with its configuration including licensing, OAuth providers, feature flags, health status, and deployment statistics.
template-parameter
A user-supplied variable defined in a template version that customizes workspace provisioning (e.g., region, instance type). Parameters have types, validation rules, default values, and mutable/immutable flags.
external-auth
A linked OAuth2 provider (GitHub, GitLab, Bitbucket, Azure DevOps) configured on a Coder deployment. Workspace agents use external auth tokens to clone private repositories and authenticate to external services.