The API Report CardAPI Index
PetDesk

PetDesk API

petdesk.com

No public developer API, portal, or OAuth flow. The documented integration pattern is one way: a PIMS like ezyVet issues credentials that clinics email to PetDesk so it can consume the PIMS API. There is no self-serve way to read appointments, messages, calls, or reviews back out.

Last verified: July 2026Healthcare
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceFAILNo public or documented developer API; the only integration pattern is one way, with PIMS credentials emailed to PetDesk.
AccessFAILOnboarding means a clinic emailing PIMS credentials to integrations@petdesk.com; outside developers get no path in.
CoveragePOORData flows from the PIMS into PetDesk only; appointments, message threads, calls, and reviews cannot be pulled out.
AuthFAILPetDesk holds clinic-supplied PIMS client secrets sent by email; it issues no OAuth or tokens of its own.
Docs & DXFAILHelp centers carry end-user articles only; no API reference, portal, sandbox, or general webhook spec.
StabilityMIXEDAcquired products Vetstoria, WhiskerCloud, and Kontak kept separate backends, so there is no single surface to target.
Supergood: PetDesk isn't going to ship an API, so we did: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

PetDesk scores F on the API Report Card. No public developer API, portal, or OAuth flow. The documented integration pattern is one way: a PIMS like ezyVet issues credentials that clinics email to PetDesk so it can consume the PIMS API. There is no self-serve way to read appointments, messages, calls, or reviews back out.

Tried to integrate with PetDesk?
SOURCES
No public REST API, OAuth flow, or developer portal, third-party tools cannot pull a clinic's PetDesk data (appointments, messages, calls, forms, reviews, payments) programmatically petdesk.com β†—
Integration model is unidirectional from PIMS into PetDesk, clinics hand over PIMS API credentials to integrations@petdesk.com, with no equivalent way to pull data out of PetDesk docs.ezyvet.com β†—
Integration coverage is limited to PetDesk-built PIMS connectors; if a practice's PIMS is not on the 30+ supported list, there is no fallback API path petdesk.com β†—
Some PIMS integrations are read-only (e.g., Scribe runs in 'Read Only mode' against several PIMS) so written outputs can't post back to the record of truth petdesk.com β†—
Multiple settings (reminder timing, message templates, integration sync windows) can only be changed by PetDesk staff, which functions as a programmatic-access gap for the practice itself capterra.com β†—
Acquired-product fragmentation, Vetstoria, WhiskerCloud, and Kontak each came with their own backends, so there is no single unified API even internally for third parties to target pillsburylaw.com β†—
Pricing creep and a-la-carte module fees, starts around $389/month for the base mobile app and adds $200+/month for Vetstoria-powered Direct Booking, with users reporting the total cost outgrows the value vetsoftwarehub.com β†—
Reminder timezone bugs, clients receive reminders in the wrong timezone and PetDesk's only fix was to ask clients to delete and reinstall the app, which is infeasible at scale capterra.com β†—
Text/SMS sync lag with the PIMS, with messages not consistently writing back to the patient record softwareadvice.com β†—
Many configuration changes (reminder timing, templates) can only be made by PetDesk staff, not the practice, painful during holidays or after-hours capterra.com β†—
PIMS integration described as shallow for some systems, practices end up managing data in two places vetsoftwarehub.com β†—
Long support response times reported, including one user waiting ~1.5 months for a resolution pissedconsumer.com β†—
PetDesk Phones onboarding criticized, users report being shipped hardware with little training, login info, or handoff pissedconsumer.com β†—
Module pricing fragmentation, clinics often need 3-4 add-ons (Comms, Direct Booking, Phones, Scribe, Marketing) to get the full pitched experience getapp.com β†—