---
title: "Vettigo integration status"
method: GET
path: "/workspaces/{workspaceId}/vettigo/status"
tags: ["vettigo"]
---

# Vettigo integration status

`GET /workspaces/{workspaceId}/vettigo/status`

## Request

- Base URL: `https://vetnio.com/api/v2`
- URL: `https://vetnio.com/api/v2/workspaces/{workspaceId}/vettigo/status`
- Auth: HTTP bearer

Returns whether the calling user has a Vettigo account linked to Vetnio. The link is created when the user first opens Vetnio from inside Vettigo, cannot be set up through the REST API, and is the same in every workspace. Use it to decide whether to offer Vettigo features. Never fails: any problem is reported as `connected: false`.

## Path parameters

- `workspaceId` string, required: Identifier of the Vetnio workspace (clinic). The caller must be a member. The Vettigo clinic used is the one the caller last launched Vetnio from, not something configured on the workspace.

## Response `200`

Vettigo connection status.

- object: Whether the calling user can use the Vettigo endpoints. The link belongs to the user, not to the workspace.
  - `connected` boolean, required: `true` when the calling user has a Vettigo account linked to Vetnio, which happens the first time they open Vetnio from Vettigo. The other Vettigo endpoints return `401` while this is `false`. Also `false` when the status could not be determined.
  - `ehrIntegrationName` string, nullable, required: Name of the connected practice-management system: always `vettigo` when `connected` is `true`, otherwise `null`.

## Other responses

- `400`: Invalid input data
- `401`: Authorization not provided
- `403`: Insufficient access
- `404`: Not found
- `500`: Internal server error

---

[API](https://skmtc.dev/vetnio/apis/vetnio-api.md) - [All operations](https://skmtc.dev/vetnio/apis/vetnio-api/llms.txt) - [OpenAPI document](https://skmtc.dev/vetnio/apis/vetnio-api/revisions/d004afd5617d?raw)