How Peak Leverage connects to ezyVet

ezyVet supports outbound webhooks primarily for specific partner integrations (like insurance claims or supplier orders) rather than general event subscriptions. For generic web integrations, you typically need to poll the API or rely on write-only flows from the website.

All API endpoints are throttled per minute. Integrations should implement queueing and respect HTTP 429 (Too Many Requests) responses to minimize performance impacts on the clinic's system.

The API is versioned at the endpoint level (e.g., /v1/ vs /v2/). Integrations should lock into the specific version documented during development and monitor ezyVet release notes for deprecations.

API access requires explicit approval from ezyVet. Private API credentials must be scoped specifically to the integrating clinic, and write-back permissions incur an extra review process and monthly fee to ensure data integrity.

Peak Leverage uses native embeds when they preserve the required data capture and operator flow, and uses custom integration when more control is needed.

If the platform does not document a capability publicly, Peak Leverage does not claim it or rely on it.