This page documents the canonical HTTP contract for this endpoint.
The response example shows one representative field and object; the live catalog contains the complete workspace projection, including eligible organization custom fields. The workspace path value is an enum: leads, companies, or tasks. Developer-key scopes are enforced per concrete path: /api/workspaces/leads/column-catalog requires both leads:read and companies:read; companies requires companies:read; tasks requires tasks:read. This path-specific authorization is the effective API eligibility; the registry lists broader operation-level scopes.
Responses compose standard workspace fields, organization-specific CRM fields and, when source_table_id is supplied, source-scoped research fields. Each field includes picker identity/path/type and may include field_semantics and value_schema; resolve shared schema definitions through capability schemas. The response is dynamic for the caller's organization and source table.
Path parameters
workspacerequiredstring
leads, companies, or tasks. Each enum value has a different developer-key scope.
| Name | Type | Description |
|---|---|---|
| workspacerequired | string | leads, companies, or tasks. Each enum value has a different developer-key scope. |
Query parameters
source_table_id· optionalstring
Optional organization-scoped source table; when omitted, research columns are not included.
| Name | Type | Description |
|---|---|---|
| source_table_id | string | Optional organization-scoped source table; when omitted, research columns are not included. |
Errors
| Status | Meaning |
|---|---|
| 400 | Unsupported workspace value. |
| 401 | Authentication required or authenticated user has no organization context. |
| 403 | Developer API key lacks one of the scopes required for the selected workspace. |
