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.
openapi: 3.2.0
info:
title: ezyVet Animals Prescriptions API
description: 'The ezyVet API is a RESTful interface to ezyVet, cloud-based veterinary practice information management software (PIMS). ezyVet was founded in New Zealand in 2006 and acquired by IDEXX Laboratories in June 2021, alongside IDEXX''s Cornerstone and Neo PIMS (the acquisition also included Vet Radar).
The full API spans roughly 216 endpoints across animals/patients, contacts/clients, appointments, consultations, invoices, products, and diagnostics. Access is partner-gated: a developer must apply for an integration and receive an approved partner_id plus client_id/client_secret, then obtain a bearer token via the OAuth 2.0 Client Credentials grant. Tokens have a 12-hour TTL.
GROUNDING NOTE: The OAuth token endpoint, the /v1/contact CRUD endpoints, the Standard Diagnostic Integration, and the base/rate-limit behavior below are confirmed from ezyVet''s public developer documentation (developers.ezyvet.com). The remaining resource paths (animal, appointment, consult, invoice, product, diagnostic, prescription, vaccination and their reference resources) are MODELED on ezyVet''s documented /v1/{resource} REST pattern and published resource categories - operationId or path names may differ from the exact ezyVet catalog. Consult the partner Postman collection for authoritative request/response shapes.'
version: '1.0'
contact:
name: ezyVet Developer Portal
url: https://developers.ezyvet.com/docs/v1/
x-ownership: ezyVet is owned by IDEXX Laboratories, Inc. (acquired June 2021).
servers:
- url: https://api.ezyvet.com
description: Production
- url: https://api.trial.ezyvet.com
description: Trial / sandbox
security:
- bearerAuth: []
tags:
- name: Prescriptions
description: Prescriptions and vaccinations. (Partially confirmed.)
paths:
/v1/prescription:
get:
operationId: listPrescriptions
tags:
- Prescriptions
summary: List prescriptions
description: Lists prescriptions. A v2 prescription resource exists; v2 is recommended going forward. (Partially confirmed.)
responses:
'200':
$ref: '#/components/responses/ListResponse'
post:
operationId: createPrescription
tags:
- Prescriptions
summary: Create a prescription
requestBody:
$ref: '#/components/requestBodies/GenericResource'
responses:
'200':
$ref: '#/components/responses/ItemResponse'
'422':
$ref: '#/components/responses/ValidationError'
/v2/prescription:
get:
operationId: listPrescriptionsV2
tags:
- Prescriptions
summary: List prescriptions (v2)
description: v2 prescription resource with a GET endpoint; recommended over v1. (Referenced in developer docs.)
responses:
'200':
$ref: '#/components/responses/ListResponse'
/v1/vaccination:
get:
operationId: listVaccinations
tags:
- Prescriptions
summary: List vaccinations
description: Lists vaccination records. (Referenced in developer docs; POST/PATCH supported.)
responses:
'200':
$ref: '#/components/responses/ListResponse'
post:
operationId: createVaccination
tags:
- Prescriptions
summary: Create a vaccination
requestBody:
$ref: '#/components/requestBodies/GenericResource'
responses:
'200':
$ref: '#/components/responses/ItemResponse'
'422':
$ref: '#/components/responses/ValidationError'
components:
schemas:
Error:
type: object
properties:
error:
type: string
messages:
type: array
items:
type: string
ListEnvelope:
type: object
description: ezyVet list responses return a meta object plus an items array whose elements wrap each resource under its type key. (Shape modeled.)
properties:
meta:
type: object
properties:
items:
type: object
properties:
total:
type: integer
limit:
type: integer
page:
type: integer
pages:
type: integer
items:
type: array
items:
type: object
additionalProperties: true
requestBodies:
GenericResource:
required: true
description: Resource payload. ezyVet write bodies are resource-specific; consult the partner Postman collection for exact field lists. (Modeled as a free-form object here.)
content:
application/json:
schema:
type: object
additionalProperties: true
responses:
ListResponse:
description: A paginated list envelope.
content:
application/json:
schema:
$ref: '#/components/schemas/ListEnvelope'
ValidationError:
description: Request validation failed.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
ItemResponse:
description: A single resource envelope.
content:
application/json:
schema:
type: object
additionalProperties: true
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: Bearer access token from POST /v1/oauth/access_token (OAuth 2.0 Client Credentials). 12-hour TTL.