The API Report CardAPI Index
IDEXX Neo

IDEXX Neo API

Healthcare / EHR (Veterinary Practice Management) · idexx.com

IDEXX Neo integrates through per-clinic API keys generated in-app and emailed to approved partners; there is no public developer portal or sandbox. The separate PIMS-RT REST API (OAuth 2.0, OData v4) offers read-only practice data with 1,000-item caps and 5-second query timeouts.

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

SCORECARD

ExistenceGOODTwo real surfaces: per-clinic Neo API keys plus the PIMS-RT REST API (OAuth 2.0, OData v4) for read-only practice data.
AccessPOORPartners apply via IDEXX's Integration Request Form; clinics generate keys one practice at a time.
CoveragePOORPIMS-RT is read-only with 1,000-item response caps and 5-second query timeouts; writes stay with approved partners.
AuthPOORPer-clinic API keys are copied out of the Neo UI and emailed to the integration partner.
Docs & DXPOORNo public Neo developer portal or sandbox; technical docs are shared only after partner approval, under partner terms.
StabilityMIXEDPIMS-RT constraints are documented, but rate-limit policy and OAuth scopes are only shared under NDA.
Supergood: IDEXX Neo has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

IDEXX Neo scores D on the API Report Card. IDEXX Neo integrates through per-clinic API keys generated in-app and emailed to approved partners; there is no public developer portal or sandbox. The separate PIMS-RT REST API (OAuth 2.0, OData v4) offers read-only practice data with 1,000-item caps and 5-second query timeouts.

Tried to integrate with IDEXX Neo?
SOURCES
No public Neo developer portal, no self-serve sandbox, and no published REST/OAuth reference for the core Neo API - third parties must apply through the IDEXX Practice Management Software Integration Request Form before seeing technical documentation idexx.com
Per-clinic API key model requires the clinic admin to generate an API key in Neo and email it to the integration partner one practice at a time, multiplying enrollment friction for multi-site operators and partners scaling across the install base software.idexx.com
IDEXX Data Services / PIMS-RT API documentation does not publish rate-limit policy, OAuth scopes or partner onboarding requirements outside an NDA, making feasibility scoping impossible without contacting IDEXX io.datapointapi.com
PIMS-RT API caps responses at max 1,000 items per query with a 5-second query timeout and 30-second total request limit, constraining bulk-export and high-throughput sync use cases io.datapointapi.com
Integration approvals are a vendor-controlled choke point: IDEXX selects which categories (diagnostics, payments, client engagement, etc.) and which named partners are listed on the Neo Integrations marketplace, and users report new IDEXX-monetised integrations being prioritised over fixes softwareadvice.com
Users on the public Neo ideas portal have repeatedly requested integrations (e.g. NetSuite) that remain unimplemented, indicating long lag times between partner demand and IDEXX-approved listings idexxneo.ideas.aha.io
Integrated payments (CardConnect via IDEXX Payments) have a documented history of silent / mis-billed charges, indicating limited transparency into payment-side data flows even for approved integrations zuloai.com
Set-up of approved partner integrations (e.g. Vetsource, SmartFlow) is documented per-clinic and per-partner via Zendesk articles rather than a unified developer portal, with each partner publishing its own onboarding flow idexxneosupport.zendesk.com
Financial and accounting tracking is 'clunky' - users cannot accurately track A/R, calculate client interest charges, track billed vs. paid transactions, or generate accurate tax reports capterra.com
Inventory management is described as a 'NIGHTMARE' by multiple users, with no purchase history tracking and unreliable cost-of-goods accuracy capterra.com
Records cannot be e-mailed directly between veterinary practices or to owners, forcing manual workarounds for record sharing capterra.com
Check-in to check-out workflow can take roughly double the time of older systems, with staff frustration reported after 9+ months of daily use softwareadvice.com
Billing disputes: practices report being charged for Neo before the system was fully up and running, with only partial refunds issued after cancellation zuloai.com
Integrated CardConnect payments charged USD 40-69/month silently for months, resulting in USD 1,400+ in disputed charges and only ~USD 207 in refunds per one published case zuloai.com
Release cadence has slowed - users report 'development has come to a virtual standstill,' with releases months apart that contain only minor fixes and new revenue-generating IDEXX integrations softwareadvice.com
Reporting and data export are limited compared to ezyVet/Cornerstone, with users routing around Neo via manual extracts g2.com
Limited third-party app integration breadth versus the broader cloud PIMS market, despite a published 'Neo Integrations' page software.idexx.com
Vendor lock-in - Neo is tightly bundled with IDEXX diagnostics (VetConnect Plus, Web PACS), IDEXX Payments and IDEXX-owned partner integrations, raising clinician-choice concerns inside the IDEXX vertical-integration debate dvm360.com