Shepherd Veterinary Software User API
The User API from Shepherd Veterinary Software — 1 operation(s) for user.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/shepherd-vet:shepherd-vet-user-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
version: v1
title: Shepherd Open API (v2.248.0.39) User API
description: 'Production Base URL: https://open-api.shepherd.vet/pav2/
Production App URL: https://app.shepherd.vet/
Production Documentation URL: https://app.shepherd.vet/swagger/
Sandbox Base URL: https://demo-open-api.shepherd.vet/pav2/
Sandbox App URL: https://demo.shepherd.vet/
Sandbox Documentation URL: https://demo.shepherd.vet/swagger
Authorization: The integration is authorized by providing two headers in the API call
X-Integration-Private-Key - this contains the private key from your credentials
X-Integration-Public-Key - this contains the public key from your credentials
Additionally, for all requests other than Clinic, the X-Clinic-Id header must be provided with the value of the clinic entity id for which you are running the API requests. You can get the entity id by calling the Clinic endpoint. If authorization fails, the request returns HTTP status 401 and the response body is one of the messages below. Missing X-Integration-Public-Key header - the public key header is absent from the request. Missing X-Integration-Private-Key header - the private key header is absent from the request. Missing X-Clinic-Id header - the clinic identifier header is absent, and the endpoint is clinic scoped. Incorrect API keys provided - both key headers were supplied, but the public key matches no integration, or the private key is not valid for that integration. Integration not enabled for the provided clinic - the key pair is valid, but the integration is not enabled and active for the clinic supplied in X-Clinic-Id. NEW: Each API call will count against your RPH and RPM limits. Once you exhaust those limits, requests will start returning HTTP status 429. The RPH is set to 12000 and RPM to 800 (subject to change). Where an endpoint supports searchQuery, a query longer than 500 characters may return HTTP status 400 with ERROR_MESSAGES.SEARCH_PHRASE.TOO_LONG, and a query with more than 10 words may return HTTP status 400 with ERROR_MESSAGES.SEARCH_PHRASE.TOO_MANY_PHRASES. NOTE: Since this API is WIP, we would be happy to hear any feedback and to implement additional filtering/sorting options etc. **Endpoints:
All endpoints are POST requests that accept JSON bodies. The common request properties for all endpoints are:**
rpp::int - The number of items to return per page. The max is 1000. Defaults to 10. page::int - The page number. Defaults to 1. sort::string - Which field to sort by. Needs to be in "field|order" format, where order is either "asc" or "desc". All top-level properties should be sortable, only some nested-fields work and you should probably not use them until this API reaches production and we settle on which nested-field sortings we will support. Default depends on endpoint, usually "id|asc". embed::string - Comma-separated values for nested-fields you want to fetch (eg. "clientPhones,clientPhones.phoneType" on Client endpoint). If a specific embed is not requested, the response will contain either null or an empty array for that value. No default. dateCreatedFrom::date
dateCreatedTo::date
dateUpdatedFrom::date
dateUpdatedTo::date
- Date range filters for either the creation date or last update date. - You can pass in either one end or both of them. *
* Only the date filters listed on an endpoint''s request model are supported; sending another one, or a ''From'' later than its ''To'', returns HTTP status 400. The request responses will come back as a JSON object. The common response properties for all endpoints are:
embed::string - Lists the embed used in the request. This may sometimes be different from what you sent in, if in the future we add that some embeds get set automatically on certain endpoints
links::object[] - Always empty, a leftover from the internal framework we use on our web API. Will be removed in the future if possible so do not rely on this
page::int - Which page was fetched.'
servers:
- url: https://open-api.shepherd.vet
tags:
- name: User
paths:
/pav2/open-api-users:
post:
tags:
- User
summary: Retrieves {OpenApiUserController.Pav2User} resources that match the specified…
description: 'Example Request
{
"embed": "roles",
"rpp": 1
}
Example Response
{
"embed": "roles",
"item": [
{
"clinicUser": [],
"coreUser": {
"firstName": "Lana",
"id": "c1d78fa3-2c64-4f6a-9e07-44238fa017c3",
"isApproved": true,
"isLockedOut": false,
"lastName": "Horvat",
"userName": "LANAH_shepherd.dev.fake"
},
"id": "c1d78fa3-2c64-4f6a-9e07-44238fa017c3",
"licenseNumber": "HR-998812",
"prefix": "Dr.",
"roles": [
{
"description": "User with full system access.",
"id": "5a91d97e-6e71-42db-9c5b-c810ee7d76e0",
"roleName": "Admin"
}
],
"suffix": "DVM",
"userId": "c1d78fa3-2c64-4f6a-9e07-44238fa017c3",
"userLicenseType": null,
"userLicenseTypeId": "f4414e61-94f3-45e1-8823-f8b2a7e1b5d1",
"dateCreated": "2025-08-05T15:22:47.211Z",
"dateUpdated": "2025-08-06T09:03:12.486Z"
}
],
"links": [],
"page": 1,
"recordsPerPage": 1,
"searchQuery": null,
"sort": null,
"totalRecords": 2
}'
operationId: OpenApiUserGet
parameters:
- name: x-integration-public-key
in: header
description: Your public API key
required: true
schema:
type: string
- name: x-integration-private-key
in: header
description: Your private API key
required: true
schema:
type: string
- name: x-clinic-id
in: header
description: The clinic uuid identifier
required: true
schema:
type: string
responses:
'200':
description: A paged collection of users matching the search criteria.
content:
application/json:
schema:
$ref: '#/components/schemas/RESTCollectionModelBase_OpenApiUserController.Pav2User'
text/json:
schema:
$ref: '#/components/schemas/RESTCollectionModelBase_OpenApiUserController.Pav2User'
application/hal+json:
schema:
$ref: '#/components/schemas/RESTCollectionModelBase_OpenApiUserController.Pav2User'
'401':
description: 'Authorization failed. One of: Missing X-Integration-Public-Key header, Missing X-Integration-Private-Key header, Missing X-Clinic-Id header, Incorrect API keys provided, or Integration not enabled for the provided clinic.'
'429':
description: Request rate limit exceeded. Please wait before making further requests. Returned once the integration passes its configured hourly or per-minute request allowance.
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/OpenApiUserController.UserFilterModel'
text/json:
schema:
$ref: '#/components/schemas/OpenApiUserController.UserFilterModel'
application/hal+json:
schema:
$ref: '#/components/schemas/OpenApiUserController.UserFilterModel'
description: The model.
required: true
components:
schemas:
RESTCollectionModelBase_OpenApiUserController.Pav2User:
type: object
properties:
embed:
type: string
item:
type: array
items:
$ref: '#/components/schemas/OpenApiUserController.Pav2User'
page:
format: int32
type: integer
recordsPerPage:
format: int32
type: integer
searchQuery:
type: string
sort:
type: string
totalRecords:
format: int32
type: integer
OpenApiUserController.Pav2User:
description: Pav2User rest model.
type: object
properties:
clinicUser:
description: List of objects representing the clinic User info entites.
type: array
items:
$ref: '#/components/schemas/OpenApiUserController.ClinicUser'
coreUser:
$ref: '#/components/schemas/OpenApiUserController.UserInfo'
description: Object representing UserInfo entity.
id:
description: Unique identifier representing the User.
type: string
licenseNumber:
description: User's license number.
type: string
prefix:
description: User's assigned prefix (e.g., "Dr.", "Mr.", "Mrs.").
type: string
roles:
description: List of objects representing User role info entities.
type: array
items:
$ref: '#/components/schemas/OpenApiUserController.Role'
suffix:
description: User's assigned suffix (e.g., "MD", "PhD", "Jr.").
type: string
userId:
format: uuid
description: Unique identifier representing the User.
type: string
example: 00000000-0000-0000-0000-000000000000
userLicenseType:
$ref: '#/components/schemas/OpenApiUserController.UserLicenseType'
description: Object representing the Type of the user license.
userLicenseTypeId:
description: Unique identifier representing the related User license type entity.
type: string
dateCreated:
format: date-time
type: string
dateUpdated:
format: date-time
type: string
OpenApiUserController.ClinicUser:
description: ClinicUser REST model.
type: object
properties:
clinicId:
format: uuid
description: Unique identifier representing the related Clinic entity.
type: string
example: 00000000-0000-0000-0000-000000000000
isTimeClockEnabled:
description: Flag indicating if Time clock (employee time tracking) is enabled.
type: boolean
userId:
format: uuid
description: Unique identifier representing the related User entity.
type: string
example: 00000000-0000-0000-0000-000000000000
dateCreated:
format: date-time
type: string
dateUpdated:
format: date-time
type: string
id:
type: string
OpenApiUserController.Role:
description: Role REST model.
type: object
properties:
description:
description: Role description.
type: string
id:
description: Unique identifier representing this role.
type: string
roleName:
description: Role name.
type: string
OpenApiUserController.UserFilterModel:
description: User Filter REST model
type: object
properties:
isApproved:
description: Filters by IsApproved status. Defaults to null, returns both active and inactive users.
type: boolean
isLockedOut:
description: Filters by IsLockedOut status. Defaults to null, returns both locked out and not locked out users.
type: boolean
searchQuery:
description: Filters by user first name, last name and email.
type: string
dateCreatedFrom:
format: date-time
description: 'Sets the start of the date range filter on the entity creation date. Must not be later than DateCreatedTo, or
the request returns 400. Defaults to null.'
type: string
dateCreatedTo:
format: date-time
description: The end of the date range filter on the entity creation date. Defaults to null.
type: string
dateUpdatedFrom:
format: date-time
description: 'The start of the date range filter on the entity last update date. Must not be later than DateUpdatedTo, or the
request returns 400. Defaults to null.'
type: string
dateUpdatedTo:
format: date-time
description: The end of the date range filter on the entity last update date. Defaults to null.
type: string
embed:
description: Comma-separated list of embedded properties to fetch. Nested fetches can be specified using dot notation (e.g., "client.clientPhones"). Defaults to null.
type: string
excludeIds:
description: Comma-separated list of IDs representing entities that you wish to exclude from your search. Defaults to null.
type: string
ids:
description: Comma-separated list of IDs representing entities that you wish to include in your search. Defaults to null.
type: string
page:
format: int32
description: The page number. Defaults to 1.
type: integer
rpp:
format: int32
description: The number of items to return per page. The max is 1000. Defaults to 10.
type: integer
sort:
description: Which field to sort by. Needs to be in "field|order" format, where order is either "asc" or "desc". The default sort field depends on the endpoint, typically "id|asc"
type: string
OpenApiUserController.UserInfo:
description: CoreUser REST model.
type: object
properties:
firstName:
description: User's first name.
type: string
id:
description: Unique identifier representing the User.
type: string
isApproved:
description: 'Flag indicating if a user is approved. If approved it will be listed under a list of Active
users in application, otherwise it will be listed under Inactive users.'
type: boolean
isLockedOut:
description: Flag indicating if a user is locked out. If true, this user won't be able to log into the application.
type: boolean
lastName:
description: User's last name.
type: string
userName:
description: Username of the user.
type: string
OpenApiUserController.UserLicenseType:
description: UserLicenseType REST model
type: object
properties:
abrv:
description: Short unique identifier for the lookup.
type: string
description:
description: The description of the lookup entry.
type: string
name:
description: The name of the lookup entry.
type: string
dateCreated:
format: date-time
type: string
dateUpdated:
format: date-time
type: string
id:
type: string