---
title: "Get the clinic"
description: "The clinic a connection signs in to: its name, its SIIPS address, its timezone (every startsAt the clinical operations answer carries its offset) and its cost centres, with the one a call that names none runs at. Another organization's connection answers CONNECTION_NOT_FOUND. Contains no patient data and performs no clinical login.\n\n- **Scopes:** any one of `visoft:appointments:read`, `visoft:appointments:write`, `visoft:connections:read`, `visoft:connections:write`\n- **Credentials:** an API key, a client-credentials token or a person's access token\n- **Effect:** read-only; safe to retry\n- **Limits:** response up to 1 MB\n- **CLI:** `arbol visoft clinic get` · **MCP tool:** `visoft_clinic_get`"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.getarbol.com/llms.txt
> Use this file to discover all available pages before exploring further.

Path: Visoft API › Clinic

`GET /v1/visoft/clinic`

The clinic a connection signs in to: its name, its SIIPS address, its timezone (every startsAt the clinical operations answer carries its offset) and its cost centres, with the one a call that names none runs at. Another organization's connection answers CONNECTION_NOT_FOUND. Contains no patient data and performs no clinical login.

- **Scopes:** any one of `visoft:appointments:read`, `visoft:appointments:write`, `visoft:connections:read`, `visoft:connections:write`
- **Credentials:** an API key, a client-credentials token or a person's access token
- **Effect:** read-only; safe to retry
- **Limits:** response up to 1 MB
- **CLI:** `arbol visoft clinic get` · **MCP tool:** `visoft_clinic_get`

## Authentication

Requires one of the following:

- `arbolHuman`, oauth2, scopes: `visoft:appointments:read`
- `arbolHuman`, oauth2, scopes: `visoft:appointments:write`
- `arbolHuman`, oauth2, scopes: `visoft:connections:read`
- `arbolHuman`, oauth2, scopes: `visoft:connections:write`
- `arbolMachine`, oauth2, scopes: `visoft:appointments:read`
- `arbolMachine`, oauth2, scopes: `visoft:appointments:write`
- `arbolMachine`, oauth2, scopes: `visoft:connections:read`
- `arbolMachine`, oauth2, scopes: `visoft:connections:write`
- `arbolApiKey`, http, header `Authorization`

## Query parameters

- `connectionId` (`visoft.clinic.get.query.connectionId`; string, optional) — The connection whose clinic to read. Optional when the organization has one Visoft connection; required when it has several.
  - minLength 5; maxLength 68; pattern `^con_[0-9A-Za-z]+$`

## Code samples

### cURL

```bash
curl https://api.getarbol.com/v1/visoft/clinic \
  --header "Authorization: Bearer $ARBOL_API_KEY"
```

### TypeScript

```typescript
import { createClient } from "@arbol-ai/sdk";

const arbol = createClient({
  baseUrl: "https://api.getarbol.com",
  token: process.env.ARBOL_API_KEY!,
});

const { data } = await arbol.visoft.clinic.get();
```

### Rust

```rust
use arbol_sdk::{types, Client, Credential};

let arbol = Client::new(Credential::ApiKey(std::env::var("ARBOL_API_KEY")?))?;

let data = arbol
    .visoft()
    .clinic()
    .get(&types::VisoftClinicGetInput::default())
    .await?;
```

### CLI

```bash
arbol visoft clinic get
```

### MCP

```json
{
  "name": "visoft_clinic_get",
  "arguments": {}
}
```

## Responses

### 200

Successful operation.

#### Example

```json
{
  "success": true,
  "data": {
    "id": "string",
    "name": "string",
    "clinicalSystem": "http://example.com",
    "timezone": "string",
    "agencies": [
      {
        "code": "string",
        "label": "string"
      }
    ],
    "defaultAgencyCode": "string"
  },
  "error": null,
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`visoft.clinic.get.response.200.success`; boolean, required)
  - one of `true`
- `data` (`visoft.clinic.get.response.200.data`; object, required)
  - `id` (`visoft.clinic.get.response.200.data.id`; string, required) — The clinic, as a connection names it (`clinicId`).
  - `name` (`visoft.clinic.get.response.200.data.name`; string, required) — The clinic's name.
  - `clinicalSystem` (`visoft.clinic.get.response.200.data.clinicalSystem`; string, required) — The clinic's SIIPS address.
    - format `uri`
  - `timezone` (`visoft.clinic.get.response.200.data.timezone`; string, required) — The clinic's IANA timezone: SIIPS writes every agenda in its wall time, and every startsAt the clinical operations answer carries its offset.
  - `agencies` (`visoft.clinic.get.response.200.data.agencies`; array<object>, required) — The clinic's cost centres, in the order SIIPS lists them: contracts, services, agendas and cancellations belong to one of them.
    - `code` (`visoft.clinic.get.response.200.data.agencies.code`; string, required) — The cost centre's SIIPS code.
      - pattern `^\d{3}$`
    - `label` (`visoft.clinic.get.response.200.data.agencies.label`; string, required) — The cost centre's name.
  - `defaultAgencyCode` (`visoft.clinic.get.response.200.data.defaultAgencyCode`; string | null, required) — The cost centre a clinical call that names no agencyCode runs at; null when every call must name one.
    - pattern `^\d{3}$`
- `error` (`visoft.clinic.get.response.200.error`; unknown, required)
- `metadata` (`visoft.clinic.get.response.200.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`visoft.clinic.get.response.200.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 400

`INVALID_INPUT`: The request does not match the published schema.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "INVALID_INPUT",
    "message": "string",
    "retryable": false,
    "data": {
      "issues": [
        {
          "path": "string",
          "message": "string"
        }
      ]
    }
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`visoft.clinic.get.response.400.success`; boolean, required)
  - one of `false`
- `data` (`visoft.clinic.get.response.400.data`; unknown, required)
- `error` (`visoft.clinic.get.response.400.error`; object, required) — The request does not match the published schema.
  - `code` (`visoft.clinic.get.response.400.error.code`; string, required) — The failure code, stable across releases.
    - one of `"INVALID_INPUT"`
  - `message` (`visoft.clinic.get.response.400.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`visoft.clinic.get.response.400.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`visoft.clinic.get.response.400.error.data`; object, required)
    - `issues` (`visoft.clinic.get.response.400.error.data.issues`; array<object>, optional)
      - `path` (`visoft.clinic.get.response.400.error.data.issues.path`; string, required) — RFC 6901 JSON Pointer to the refused field; empty for the whole input.
        - maxLength 256
      - `message` (`visoft.clinic.get.response.400.error.data.issues.message`; string, required)
        - maxLength 256
- `metadata` (`visoft.clinic.get.response.400.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`visoft.clinic.get.response.400.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 401

`UNAUTHORIZED`: A valid access token is required.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "UNAUTHORIZED",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`visoft.clinic.get.response.401.success`; boolean, required)
  - one of `false`
- `data` (`visoft.clinic.get.response.401.data`; unknown, required)
- `error` (`visoft.clinic.get.response.401.error`; object, required) — A valid access token is required.
  - `code` (`visoft.clinic.get.response.401.error.code`; string, required) — The failure code, stable across releases.
    - one of `"UNAUTHORIZED"`
  - `message` (`visoft.clinic.get.response.401.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`visoft.clinic.get.response.401.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`visoft.clinic.get.response.401.error.data`; object, required) — No fields.
- `metadata` (`visoft.clinic.get.response.401.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`visoft.clinic.get.response.401.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 403

`FORBIDDEN`: The token does not authorize this operation.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "FORBIDDEN",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`visoft.clinic.get.response.403.success`; boolean, required)
  - one of `false`
- `data` (`visoft.clinic.get.response.403.data`; unknown, required)
- `error` (`visoft.clinic.get.response.403.error`; object, required) — The token does not authorize this operation.
  - `code` (`visoft.clinic.get.response.403.error.code`; string, required) — The failure code, stable across releases.
    - one of `"FORBIDDEN"`
  - `message` (`visoft.clinic.get.response.403.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`visoft.clinic.get.response.403.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`visoft.clinic.get.response.403.error.data`; object, required) — No fields.
- `metadata` (`visoft.clinic.get.response.403.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`visoft.clinic.get.response.403.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 404

`CONNECTION_NOT_FOUND`: The organization has no such connection.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "CONNECTION_NOT_FOUND",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`visoft.clinic.get.response.404.success`; boolean, required)
  - one of `false`
- `data` (`visoft.clinic.get.response.404.data`; unknown, required)
- `error` (`visoft.clinic.get.response.404.error`; object, required) — The organization has no such connection.
  - `code` (`visoft.clinic.get.response.404.error.code`; string, required) — The failure code, stable across releases.
    - one of `"CONNECTION_NOT_FOUND"`
  - `message` (`visoft.clinic.get.response.404.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`visoft.clinic.get.response.404.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`visoft.clinic.get.response.404.error.data`; object, required) — No fields.
- `metadata` (`visoft.clinic.get.response.404.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`visoft.clinic.get.response.404.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 409

`CONNECTION_NOT_CONFIGURED`: The organization has no active Visoft connection for this call; an administrator connects Visoft in Account.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "CONNECTION_NOT_CONFIGURED",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`visoft.clinic.get.response.409.success`; boolean, required)
  - one of `false`
- `data` (`visoft.clinic.get.response.409.data`; unknown, required)
- `error` (`visoft.clinic.get.response.409.error`; object, required) — The organization has no active Visoft connection for this call; an administrator connects Visoft in Account.
  - `code` (`visoft.clinic.get.response.409.error.code`; string, required) — The failure code, stable across releases.
    - one of `"CONNECTION_NOT_CONFIGURED"`
  - `message` (`visoft.clinic.get.response.409.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`visoft.clinic.get.response.409.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`visoft.clinic.get.response.409.error.data`; object, required) — No fields.
- `metadata` (`visoft.clinic.get.response.409.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`visoft.clinic.get.response.409.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 429

`RATE_LIMITED`: The request rate limit was exceeded. Try again later.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "RATE_LIMITED",
    "message": "string",
    "retryable": true,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`visoft.clinic.get.response.429.success`; boolean, required)
  - one of `false`
- `data` (`visoft.clinic.get.response.429.data`; unknown, required)
- `error` (`visoft.clinic.get.response.429.error`; object, required) — The request rate limit was exceeded. Try again later.
  - `code` (`visoft.clinic.get.response.429.error.code`; string, required) — The failure code, stable across releases.
    - one of `"RATE_LIMITED"`
  - `message` (`visoft.clinic.get.response.429.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`visoft.clinic.get.response.429.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `true`
  - `data` (`visoft.clinic.get.response.429.error.data`; object, required) — No fields.
- `metadata` (`visoft.clinic.get.response.429.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`visoft.clinic.get.response.429.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 500

`INTERNAL_ERROR`: The service could not complete the operation.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "INTERNAL_ERROR",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`visoft.clinic.get.response.500.success`; boolean, required)
  - one of `false`
- `data` (`visoft.clinic.get.response.500.data`; unknown, required)
- `error` (`visoft.clinic.get.response.500.error`; object, required) — The service could not complete the operation.
  - `code` (`visoft.clinic.get.response.500.error.code`; string, required) — The failure code, stable across releases.
    - one of `"INTERNAL_ERROR"`
  - `message` (`visoft.clinic.get.response.500.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`visoft.clinic.get.response.500.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`visoft.clinic.get.response.500.error.data`; object, required) — No fields.
- `metadata` (`visoft.clinic.get.response.500.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`visoft.clinic.get.response.500.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 502

`OUTCOME_UNKNOWN`: The operation may have been applied; check its result before repeating it.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "OUTCOME_UNKNOWN",
    "message": "string",
    "retryable": false,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`visoft.clinic.get.response.502.success`; boolean, required)
  - one of `false`
- `data` (`visoft.clinic.get.response.502.data`; unknown, required)
- `error` (`visoft.clinic.get.response.502.error`; object, required) — The operation may have been applied; check its result before repeating it.
  - `code` (`visoft.clinic.get.response.502.error.code`; string, required) — The failure code, stable across releases.
    - one of `"OUTCOME_UNKNOWN"`
  - `message` (`visoft.clinic.get.response.502.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`visoft.clinic.get.response.502.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `false`
  - `data` (`visoft.clinic.get.response.502.error.data`; object, required) — No fields.
- `metadata` (`visoft.clinic.get.response.502.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`visoft.clinic.get.response.502.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 503

`UPSTREAM_UNAVAILABLE`: The upstream service could not complete the request.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "UPSTREAM_UNAVAILABLE",
    "message": "string",
    "retryable": true,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`visoft.clinic.get.response.503.success`; boolean, required)
  - one of `false`
- `data` (`visoft.clinic.get.response.503.data`; unknown, required)
- `error` (`visoft.clinic.get.response.503.error`; object, required) — The upstream service could not complete the request.
  - `code` (`visoft.clinic.get.response.503.error.code`; string, required) — The failure code, stable across releases.
    - one of `"UPSTREAM_UNAVAILABLE"`
  - `message` (`visoft.clinic.get.response.503.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`visoft.clinic.get.response.503.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `true`
  - `data` (`visoft.clinic.get.response.503.error.data`; object, required) — No fields.
- `metadata` (`visoft.clinic.get.response.503.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`visoft.clinic.get.response.503.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.

### 504

`UPSTREAM_TIMEOUT`: The upstream service did not respond before its deadline.

#### Example

```json
{
  "success": false,
  "data": null,
  "error": {
    "code": "UPSTREAM_TIMEOUT",
    "message": "string",
    "retryable": true,
    "data": {}
  },
  "metadata": {
    "requestId": "string"
  }
}
```

- `success` (`visoft.clinic.get.response.504.success`; boolean, required)
  - one of `false`
- `data` (`visoft.clinic.get.response.504.data`; unknown, required)
- `error` (`visoft.clinic.get.response.504.error`; object, required) — The upstream service did not respond before its deadline.
  - `code` (`visoft.clinic.get.response.504.error.code`; string, required) — The failure code, stable across releases.
    - one of `"UPSTREAM_TIMEOUT"`
  - `message` (`visoft.clinic.get.response.504.error.message`; string, required) — What went wrong, for people; it never contains input values.
  - `retryable` (`visoft.clinic.get.response.504.error.retryable`; boolean, required) — Whether repeating the same request may succeed.
    - one of `true`
  - `data` (`visoft.clinic.get.response.504.error.data`; object, required) — No fields.
- `metadata` (`visoft.clinic.get.response.504.metadata`; object, required) — What every answer carries besides its data or error.
  - `requestId` (`visoft.clinic.get.response.504.metadata.requestId`; string, required) — Request correlation identifier, also sent as X-Request-Id.


Source: https://docs.getarbol.com/api/visoft/clinic/get/index.md