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

# VetManager integration status

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

## Request

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

Returns whether the calling user has a VetManager account linked to Vetnio. The link is created when the user opens Vetnio from a VetManager visit and cannot be set up through the REST API. Use it to decide whether to offer VetManager export. 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. Patient and visit endpoints also require the workspace to be linked to the caller's VetManager practice.

## Response `200`

VetManager connection status.

- object: Whether the calling user can use the VetManager endpoints.
  - `connected` boolean, required: `true` when the calling user has a VetManager account linked to Vetnio, created the first time they open Vetnio from a VetManager visit. Also `false` when the status could not be determined.

## 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)