The API Report CardAPI Index
Petly Plans

Petly Plans API

Healthcare / EHR (Veterinary Wellness Plan Management) · software.idexx.com

No public API. Petly Plans data moves only through closed syncs into Cornerstone, ezyVet, and Neo plus a per-practice Authorize.Net gateway. Third-party access starts at IDEXX's integration request form and manual partnership review; there is no portal, spec, or sandbox.

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

SCORECARD

ExistencePOORNo API for Petly Plans; plan and billing data moves only through closed syncs into Cornerstone, ezyVet, and Neo.
AccessPOORThird parties go through IDEXX's integration request form and a manual partnership review before any access.
CoveragePOORPlan enrollment, utilization, and recurring billing have no endpoints anywhere, not even in the adjacent Cornerstone OData API.
AuthPOORNo credentials exist to issue; recurring payment tokens sit locked in a per-practice Authorize.Net CIM vault.
Docs & DXPOORNo developer portal, OpenAPI spec, or sandbox; integration behavior is documented only in PIMS help articles.
StabilityMIXED
Supergood: Petly Plans has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Petly Plans scores D on the API Report Card. No public API. Petly Plans data moves only through closed syncs into Cornerstone, ezyVet, and Neo plus a per-practice Authorize.Net gateway. Third-party access starts at IDEXX's integration request form and manual partnership review; there is no portal, spec, or sandbox.

Tried to integrate with Petly Plans?
SOURCES
No public developer portal, OpenAPI spec, or sandbox for Petly Plans - third-party tools cannot programmatically read plan enrollment, MRR, or utilization data software.idexx.com
Any third-party integration must be requested through IDEXX's general Practice Management Software Integration Request Form and reviewed by IDEXX partnerships before access is granted idexx.com
Payment data is locked inside the Authorize.Net CIM vault provisioned per-practice, so practices cannot easily export the underlying card/ACH tokens or move to another processor without losing recurring billing idexx.com
Plan utilization and discount reconciliation is documented only as a server-side Cornerstone integration and surfaces through PIMS reports rather than an API cornerstonehelphub.com
IDEXX's adjacent Cornerstone API (datapointapi.com) is OData-only and is not positioned as a Petly Plans data source - there is no published mapping from Cornerstone OData entities to Petly Plans plan/enrollment objects io.datapointapi.com
ezyVet's partner API (also IDEXX) requires a 6-month certification window, 5-site beta, and one-time + monthly per-hospital fees, which raises the bar for any third party trying to combine Petly Plans data with ezyVet ezyvet.com
Long implementation timeline means practices wait months before plans are fully operational and revenue-generating capterra.com
Limited customization and optimization options - practices report difficulty tailoring plan bundles, discount logic, and reporting beyond the standard templates capterra.com
Effective only within the IDEXX ecosystem - practices not on Cornerstone, ezyVet, or Neo get a degraded experience with manual reconciliation capterra.com
Insufficient client-communication and review-generation features compared to standalone wellness vendors capterra.com
Service outages and degraded performance tracked by third-party status monitor since October 2025, including an April 2026 warning incident statusgator.com
Monthly draft is fixed to the 20th of each month, limiting practices that want flexible billing dates per client software.idexx.com
Practices must set up and maintain a separate Authorize.Net merchant account, adding onboarding friction and a second vendor relationship idexx.com
Plan utilization and remaining-allowance visibility depends on tight PIMS sync - practices on legacy or non-IDEXX PIMS report reconciliation pain cornerstonehelphub.com