vetmanager

Preview recovering an existing VetManager visit

For a pending creation that can no longer be retried: checks that the VetManager visit with the given id belongs to the same owner, animal, account and practice, and returns it for confirmation. Changes nothing. The vet must have opened that visit from VetManager once so Vetnio holds its access.

Errors: 400 when the visit's owner or animal differ; 401 when the visit has not been opened from VetManager; 403 for another account or practice; 409 when the pending creation changed or the visit is locked.

post/workspaces/{workspaceId}/consultations/{consultationId}/vetmanager/visit/recovery-preview

Request

Base URL
https://vetnio.com/api/v2
URL
https://vetnio.com/api/v2/workspaces/{workspaceId}/consultations/{consultationId}/vetmanager/visit/recovery-preview
Auth
HTTP bearer

Path parameters

workspaceIdstring required

Identifier of the clinic (workspace), as returned by GET /workspaces. The key's user must be a member of the clinic, or an admin of the organization it belongs to.

Example:furunculotic-loud-chihuahua

consultationIdstring required

Identifier of the consultation (UUID), as returned when it was created or by GET /workspaces/{workspaceId}/consultations. It must belong to the clinic in workspaceId.

Example:a1b2c3d4-e5f6-7890-abcd-ef1234567890

Request body

practiceIdinteger required

VetManager practice id, as returned in practice.id by the visit context.

identityKeystring required

Opaque key from the visit context. A request is rejected with 409 when the signed-in VetManager account or practice changed since it was issued.

resonIdinteger required

VetManager visit reason ("reson") id: the record the note is written to.

pendingKeystring required

pending.key from the visit context.

Example request

{
  "practiceId": 4242,
  "identityKey": "3f1e9c0b7a",
  "resonId": 2535050,
  "pendingKey": "vetnio-visit-6c1f"
}

Response

The visit that would be linked.

resonIdinteger required

VetManager visit reason ("reson") id: the record the note is written to.

namestring required

Visit reason name in VetManager.

datestring nullable required

Visit date (ISO 8601), when VetManager has one.

animalNamestring nullable required

Animal on the visit.

clientNamestring nullable required

Owner on the visit.

Example response

{
  "resonId": 2535050,
  "name": "Hälta",
  "date": "2026-10-26T09:30:00+01:00",
  "animalName": "Bella",
  "clientName": "Anna Lindqvist"
}

Changes

No recorded changes to this operation across all 1 revision of this API.