> ## Documentation Index
> Fetch the complete documentation index at: https://cadenya.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# List a tenant's subjects
> The people asserted under one tenant. Subjects have no workspace-wide list, and that is by design.
The subjects asserted under a tenant, newest first. Like tenants, subjects are never created directly: one appears when an assertion names it, on an objective or a [widget session](/docs/api-reference/widgetsessionservice/create-a-widget-session).
```typescript TypeScript theme={null}
const subjects = await client.tenants.subjects.list('external_id:acme-corp', {
workspaceId,
});
for await (const subject of subjects) {
console.log(subject.metadata.name, subject.metadata.externalId);
}
// Jordan Diaz user-42
// Casey Nguyen user-97
```
```go Go theme={null}
subjects := client.Tenants.Subjects.ListAutoPaging(ctx, "external_id:acme-corp",
cadenya.TenantSubjectListParams{WorkspaceID: cadenya.String(workspaceID)})
for subjects.Next() {
s := subjects.Current()
fmt.Println(s.Metadata.Name, s.Metadata.ExternalID)
}
```
```ruby Ruby theme={null}
subjects = cadenya.tenants.subjects.list(
"external_id:acme-corp",
workspace_id: workspace_id
)
subjects.auto_paging_each do |s|
puts "#{s.metadata.name} #{s.metadata.external_id}"
end
```
```bash cURL theme={null}
curl "https://api.cadenya.com/v1/workspaces/${WORKSPACE_ID}/tenants/external_id:acme-corp/subjects" \
-H "Authorization: Bearer ${CADENYA_API_KEY}"
```
## Subjects scope to their tenant
There is no workspace-wide subject list, because a subject's `external_id` is unique within its tenant, not across the workspace. `user-42` under Acme and `user-42` under Initech can be different people, and neither assertion knows about the other. To find a person, go through their tenant.
## Filtering
`query` does a substring match against each subject's `name` and `external_id`. `includeInfo=true` populates the per-subject `info` counts. `sortOrder`, `limit`, and `cursor` page the list the usual way; the SDK iterators follow the cursor for you.
## Related
The parent records these subjects live under.
Where a subject gets asserted alongside its tenant.
Subjects go down with their tenant.
## OpenAPI
````yaml get /v1/workspaces/{workspaceId}/tenants/{tenantId}/subjects
openapi: 3.1.0
info:
title: Cadenya API
description: API for the Cadenya Agent Runtime platform.
version: '1.0'
servers:
- url: https://api.cadenya.com
description: Production server
security:
- bearerAuth: []
tags:
- name: AIProviderKeyService
- name: APIKeyService
description: |-
Issue, rotate, disable, and revoke a workspace's API keys. Every key
belongs to exactly one workspace; the system-managed global account key is
managed via GlobalAPIKeyService instead.
- name: AccountService
description: >-
Manage the authenticated account. Accounts are the top-level
organizational
unit and contain one or more workspaces.
- name: AgentScheduleService
description: >-
Manage recurring schedules attached to agents. Schedules trigger
objectives
on a cadence defined by AgentScheduleSpec.Schedule.
- name: AgentService
description: >-
Manage AI agents within a workspace. Agents define AI behavior and tool
access.
- name: AgentVariationService
description: >-
Manage variations of an agent and their tool, sub-agent, and memory layer
assignments.
- name: GlobalAPIKeyService
description: |-
Manage the account's system-provisioned global API key. The global key is
the only key that spans every workspace; it is created by the system and
cannot be deleted, so the surface is retrieve, rotate, and the
disable/enable kill switch.
- name: MemoryService
description: >-
Manage memory layers and their entries. Layers are named containers that
can
be composed into an objective's memory cascade; entries are the keyed values
within a layer. System-managed layers (e.g., episodic layers created by the
runtime) cannot be mutated through this API.
- name: ModelService
description: |-
Manage LLM models available to a workspace. Models represent provider and
family pairs (e.g., "anthropic/claude-sonnet-4.6"). Workspaces are seeded
with the supported models and you can enable or disable each one.
- name: ObjectiveEventStreamsService
- name: ObjectiveService
- name: ProfilesService
description: |-
Operations on profiles, the account-level principals (users, API keys,
system) that authenticate against the API.
- name: SearchService
- name: TenantService
description: >-
Read and erase tenants and the subjects under them. Tenants and subjects
are
created by assertion — on objective creation or widget session mint — never
directly, so this service has no create or update: it exists to enumerate what
assertions have produced, and to destroy it on request.
- name: ToolService
description: >-
Manage tool sets and the tools they contain. Tool sets group related
tools,
and tools define specific capabilities available to agents.
When a tool set is managed, only API key actors can modify its tools; human
(profile) actors cannot.
- name: UploadService
description: |-
Issue short-lived presigned URLs for direct client-to-object-storage
uploads. Created uploads can be referenced by id when creating or updating
resources that accept binary content (e.g., MemoryEntry).
- name: WidgetService
description: |-
Manage embeddable chat widgets. A widget binds an agent to a globally
unique hostname with a per-widget origin allowlist; browsers reach it with
session tokens minted via WidgetSessionService.
- name: WidgetSessionService
description: >-
Mint and manage widget sessions. Session creation is server-to-server
only:
the customer's backend authenticates its visitor, asserts tenant/subject
context, attaches any per-visitor secrets, and receives a short-lived
bearer token the browser uses against the widget host.
- name: WorkspaceAdminService
description: >-
Administer workspaces across the account: create and archive workspaces
and
manage their membership. These operations are account-scoped and require the
admin role (a token whose profile holds the WorkOS admin role); they live
under /v1/account/workspaces rather than the workspace-scoped /v1/workspaces
tree so an admin can manage any workspace in the account, including ones they
are not themselves a member of.
- name: WorkspaceSecretService
- name: WorkspaceService
description: |-
Manage workspaces within an account. Workspaces provide organizational
grouping and isolation for resources such as agents, tools, and API keys.
This is the workspace-scoped, end-user surface. Administrative operations
(create / archive workspaces, manage members) live in WorkspaceAdminService
under /v1/account/workspaces and require the admin role.
paths:
/v1/workspaces/{workspaceId}/tenants/{tenantId}/subjects:
get:
tags:
- TenantService
- Tenants
summary: List a tenant's subjects
description: >-
Lists the subjects asserted under a tenant. Subjects are only listable
through their tenant: a subject's external_id is unique within its
tenant, not across the workspace, so the same key can name different
people under different tenants.
operationId: TenantService_ListTenantSubjects
parameters:
- name: workspaceId
in: path
description: Workspace ID.
required: true
schema:
type: string
example: workspace_01HXKD2E5NQM3T9AYWCF133E3Q
- name: tenantId
in: path
description: >-
Tenant whose subjects to list. Accepts the canonical `tenant_…` form
or
the `external_id:` form.
required: true
schema:
type: string
- name: limit
in: query
description: Maximum number of results to return.
schema:
type: integer
format: int32
- name: cursor
in: query
description: Pagination cursor from previous response.
schema:
type: string
- name: query
in: query
description: Substring match against the subject's name and external_id.
schema:
type: string
- name: sortOrder
in: query
description: Sort order for results (asc or desc by creation time).
schema:
type: string
- name: includeInfo
in: query
description: When true, the `info` field on each returned subject is populated.
schema:
type: boolean
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/ListTenantSubjectsResponse'
default:
description: Default error response
content:
application/json:
schema:
$ref: '#/components/schemas/Status'
x-codeSamples:
- lang: JavaScript
source: >-
import Cadenya from '@cadenya/cadenya';
const client = new Cadenya({
apiKey: process.env['CADENYA_API_KEY'], // This is the default and can be omitted
});
// Automatically fetches more pages as needed.
for await (const subject of client.tenants.subjects.list('tenantId',
{
workspaceId: 'workspace_01HXKD2E5NQM3T9AYWCF133E3Q',
})) {
console.log(subject.metadata);
}
- lang: Python
source: |-
import os
from cadenya import Cadenya
client = Cadenya(
api_key=os.environ.get("CADENYA_API_KEY"), # This is the default and can be omitted
)
page = client.tenants.subjects.list(
tenant_id="tenantId",
workspace_id="workspace_01HXKD2E5NQM3T9AYWCF133E3Q",
)
page = page.items[0]
print(page.metadata)
- lang: Go
source: "package main\n\nimport (\n\t\"context\"\n\t\"fmt\"\n\t\"go.cadenya.com/cadenya-go\"\n\t\"go.cadenya.com/cadenya-go/option\"\n)\n\nfunc main() {\n\tclient := cadenya.NewClient(\n\t\toption.WithAPIKey(\"My API Key\"),\n\t)\n\tpage, err := client.Tenants.Subjects.List(\n\t\tcontext.TODO(),\n\t\t\"tenantId\",\n\t\tcadenya.TenantSubjectListParams{\n\t\t\tWorkspaceID: cadenya.String(\"workspace_01HXKD2E5NQM3T9AYWCF133E3Q\"),\n\t\t},\n\t)\n\tif err != nil {\n\t\tpanic(err.Error())\n\t}\n\tfmt.Printf(\"%+v\\n\", page)\n}\n"
- lang: Ruby
source: >-
require "cadenya"
cadenya = Cadenya::Client.new(api_key: "My API Key")
page = cadenya.tenants.subjects.list("tenantId", workspace_id:
"workspace_01HXKD2E5NQM3T9AYWCF133E3Q")
puts(page)
- lang: CLI
source: |-
cadenya tenants:subjects list \
--api-key 'My API Key' \
--workspace-id workspace_01HXKD2E5NQM3T9AYWCF133E3Q \
--tenant-id tenantId
components:
schemas:
ListTenantSubjectsResponse:
type: object
properties:
items:
type: array
items:
$ref: '#/components/schemas/Subject'
pagination:
$ref: '#/components/schemas/Page'
description: List tenant subjects response.
Status:
type: object
properties:
code:
type: integer
description: >-
The status code, which should be an enum value of
[google.rpc.Code][google.rpc.Code].
format: int32
message:
type: string
description: >-
A developer-facing error message, which should be in English. Any
user-facing error message should be localized and sent in the
[google.rpc.Status.details][google.rpc.Status.details] field, or
localized by the client.
details:
type: array
items:
$ref: '#/components/schemas/GoogleProtobufAny'
description: >-
A list of messages that carry the error details. There is a common
set of message types for APIs to use.
description: >-
The `Status` type defines a logical error model that is suitable for
different programming environments, including REST APIs and RPC APIs. It
is used by [gRPC](https://github.com/grpc). Each `Status` message
contains three pieces of data: error code, error message, and error
details. You can find out more about this error model and how to work
with it in the [API Design
Guide](https://cloud.google.com/apis/design/errors).
Subject:
required:
- metadata
type: object
properties:
metadata:
$ref: '#/components/schemas/ResourceMetadata'
info:
$ref: '#/components/schemas/SubjectInfo'
description: |-
Subject is a person within a tenant as a readable record. Like Tenant it
carries no spec — `metadata.external_id` is the customer's key for them,
unique within the tenant rather than the workspace.
Page:
type: object
properties:
nextCursor:
type: string
description: >-
Page carries cursor-based pagination state. There is no total: the
cursor
walks the result set without ever counting it, and a count would cost a second
query on every list.
GoogleProtobufAny:
type: object
properties:
'@type':
type: string
description: The type of the serialized message.
additionalProperties: true
description: >-
Contains an arbitrary serialized message along with a @type that
describes the type of the serialized message.
ResourceMetadata:
required:
- id
- accountId
- workspaceId
- name
- profileId
- createdAt
type: object
properties:
id:
readOnly: true
type: string
description: >-
Unique identifier for the resource (prefixed ULID, e.g.,
"agent_01HXK...")
accountId:
readOnly: true
example: account_01HXKD2E5NQM3T9AYWCFTJHJVF
type: string
description: >-
Account this resource belongs to for multi-tenant isolation
(prefixed ULID)
workspaceId:
readOnly: true
example: workspace_01HXKD2E5NQM3T9AYWCF133E3Q
type: string
description: >-
Workspace this resource belongs to for organizational grouping
(prefixed ULID)
name:
type: string
description: >-
Human-readable name for the resource (e.g., "Customer Support
Agent", "Email Tool")
Required for resources that users interact with directly
externalId:
type: string
description: >-
External ID for the resource (e.g., a workflow ID from an external
system)
labels:
type: object
additionalProperties:
type: string
description: |-
Key-value pairs for categorization and filtering. Values are 0-63
alphanumeric characters with "-", "_", or "." allowed between; keys
follow the same shape and additionally accept an optional DNS-subdomain
prefix (e.g. "cadenya.com/") of at most 253 characters.
Examples: {"environment": "production", "team": "platform", "version": "v2"}
profileId:
readOnly: true
example: profile_01HXKD2E5NQM3T9AYWCFS0AP08
type: string
description: ID of the actor (user or service account) that created this resource
createdAt:
readOnly: true
type: string
description: Timestamp when this resource was created
format: date-time
updatedAt:
readOnly: true
type: string
description: Timestamp when this resource was last updated
format: date-time
description: >-
Standard metadata for persistent, named resources (e.g., agents, tools,
prompts)
SubjectInfo:
type: object
properties:
tenant:
readOnly: true
allOf:
- $ref: '#/components/schemas/TenantReference'
description: The tenant this subject belongs to.
objectiveCount:
readOnly: true
type: integer
description: Number of objectives associated with this subject.
format: int32
description: SubjectInfo provides read-only server-derived data about a subject.
TenantReference:
required:
- id
- externalId
type: object
properties:
id:
readOnly: true
example: tenant_01HXKD2E5NQM3T9AYWCF133E3Q
type: string
description: Cadenya's canonical tenant id.
externalId:
readOnly: true
example: acme-corp
type: string
description: The tenant identifier in the customer's namespace, as asserted.
name:
readOnly: true
example: Acme Corp
type: string
description: Human-readable name of the tenant, when one has been asserted.
description: >-
TenantReference is the read-only echo of a resource's tenant
association,
carrying both Cadenya's canonical id and the customer's own key.
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
````