
Our customers asked for a better way to collaborate on Targon. Teams want shared workloads, a single bill, and access that stays with the company, not tied to one person's login.
Organizations deliver that. Workloads, billing, and API access now live on orgs. Every account still gets a personal org for individual use. Teams get shared orgs with roles, invites, and tokens built for production pipelines.
This release makes it easier to onboard enterprises, share spend across a team, and work together across targon.com, the CLI, and the SDK.
On release, every existing account gets a newly created personal org, and all current workloads transfer into that personal org.
An organization is the tenancy boundary. It owns resources, holds billing, and receives invoices. A user remains a person's identity, login, and preferences. A membership links the two with a role.
| Scope | Stays with the user | Moves to the org |
|---|---|---|
| Identity | Email, password, 2FA, profile | - |
| Resources | - | Workloads, secrets, env vars |
| Access | Personal access tokens (PATs) | Service tokens, members, invites |
| Money | - | Credits, payment methods, invoices |
Your identity travels with you across orgs. Shared resources, billing, and access stay with the organization for the team.
Everything is an org even a solo account.
Personal orgs stay with your account for as long as you use Targon. Team orgs can be retired by an owner once active workloads and outstanding invoices are cleared.
Memberships carry one of three roles:
| Role | Permissions |
|---|---|
owner |
Full control, including deleting the org and transferring ownership. At least one required per org. |
admin |
Manage members, resources, service tokens, billing, and settings. Cannot delete the org or transfer ownership. |
member |
Create and manage resources. Cannot manage other members' resources or billing. |
Owners and admins invite teammates by email. Invitees who do not have an account yet can accept after they sign up.
There are two token types:
Personal Access Tokens (PATs) are user-scoped. They can reach every org you
belong to. Target an org by path (/orgs/{org_slug}/…). Manage PATs under
/me/api-tokens.
Service tokens are org-scoped and built for CI/CD. They belong to the org, not a person, so pipelines stay online as your team grows. The org is inferred from the token. Only owners and admins can create them. The full secret is shown once at creation.
Existing API keys become PATs at migration. Point requests at the org slug in the path (for example your personal org slug) so current integrations keep working after the move to org-scoped routes.
Billing lives on the org, so teams share one place for credits, payment methods, and invoices. Every user still has a personal org for individual spend. Team spend lives on the team org, managed by members with the right role.
Base URL: https://api.targon.com/tha/v3
Auth: Authorization: Bearer <token> (PAT or service token). Service tokens
cannot manage org membership or org settings.
| Method | Path | Purpose |
|---|---|---|
POST |
/orgs |
Create a team org |
GET |
/orgs |
List orgs you belong to |
GET |
/orgs/{org_slug} |
Org details |
PATCH |
/orgs/{org_slug} |
Update org metadata |
DELETE |
/orgs/{org_slug} |
Soft-delete a team org |
GET |
/orgs/{org_slug}/members |
List members |
GET |
/orgs/{org_slug}/members/{username} |
Member details |
PATCH |
/orgs/{org_slug}/members/{username} |
Change role |
DELETE |
/orgs/{org_slug}/members/{username} |
Remove a member |
GET |
/orgs/{org_slug}/tokens |
List service tokens |
POST |
/orgs/{org_slug}/tokens |
Create a service token |
DELETE |
/orgs/{org_slug}/tokens/{token_uid} |
Revoke a service token |
GET |
/me/api-tokens |
List PATs |
POST |
/me/api-tokens |
Create a PAT |
Workload, volume, project, template, SSH key, wallet, and credits routes live
under /orgs/{org_slug}/… as well.
Thanks for building with us,
The Targon Team
© 2026 Manifold Labs, Inc.
All Rights Reserved