Read a tool credential connection
const url = 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/tool-credentials/connections/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/tool-credentials/connections/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \ --header 'Authorization: Bearer <token>'Requires a human session in the exact current environment. Machine credentials are refused. No query parameters; responses are no-store. Secret intake is ephemeral and is never returned. Organization connections require owner or admin authority; mutation and account preview require a signed-in human session. Preview verifies current account identity without saving a connection or requiring an idempotency key. Connect independently rechecks the reviewed account digest. Connect, reconnect and revoke require a caller idempotency key; never automatically retry. A matching Connect retry returns the original immutable version even if new secret bytes are supplied; changing the secret does not rotate it.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”Verified credential metadata; never secret bytes.
object
object
object
object
Example
{ "version": { "mode": "test", "owner_kind": "user" }, "state": "active", "availability": "ready"}Headers
Section titled “Headers”Account_changed: reload and review with the signed-in account.
default
Section titled “default”Request error
object
object
Stable; branch on it. Any operation can answer invalid_request, with param naming the refused field when there is one; human_session_required, when an API key, service account or workload calls an operation only a signed-in person may perform; reauthentication_required, when a person’s sign-in is too old for the operation; permission_denied; route_not_found and method_not_allowed, when no operation matches the path or method; and feature_unavailable, when the operation’s service is not enabled on this deployment.
The request field a refusal is about, such as the agent_id or run_id query parameter; null when the refusal is not about one field.
Example
{ "error": { "action": "sign_in" }}