AtlanClient to manage Registry resources from your application. Start
with read-only calls to confirm the identity and workspace before creating
or updating anything.
Before you begin
Install SDK 0.6.0. Obtain an Atlan credential with access to the workspace you want to read. Load it from your secret store intoATLAN_TOKEN, and set
ATLAN_WORKSPACE_ID to that workspace’s ID.
These examples pass environment values explicitly. The management client
does not read a CLI session or the tracing client’s environment settings.
Connect and read
- Python
- TypeScript
Select another workspace
Use a workspace copy to make the next operation’s destination explicit:- Python
- TypeScript
with block. Copies
share its connections and credentials. A different workspace does not change
the organization or the caller’s permissions. For writes whose body requires
workspace_id (workspaceId in TypeScript), supply it in the body as well.
Find an operation
Useclient.<resource>.<method> and the
resource reference. Python methods use
snake_case; TypeScript methods use camelCase. Path arguments come first,
and a request body comes last. List methods return the operation’s response
page; follow that operation’s documented paging fields to read more.
The SDK reference describes the contracts packaged in 0.6.0. If an operation
exists in a newer HTTP reference but is absent from your client, check your
installed SDK version before changing the resource or method name.
Handle a rejected request
CatchAtlanAPIError for HTTP or transport failures and record its status,
code, and correlation ID. Do not log bearer credentials or response bodies.
Management calls make one attempt by default. See
Errors and retry middleware.
Next steps
- Register an agent: Understand the required agent metadata and identity.
- Trace your first run: Configure the separate tracing client.
- Configuration: Compare management and tracing options.