Overview
7 min
who can use the digitail api? the digitail api is available to veterinary clinics and hospital groups looking to connect digitail with internal systems such as accounting, bi dashboards, crms, or inventory tools technology partners and developers building applications or integrations that digitail clinics will actively use veterinary ecosystem partners including diagnostic labs, insurance providers, pharmacy networks, telemedicine platforms, and analytics providers that need to exchange data securely with clinics all api access is reviewed and approved by the digitail team to ensure data security, ecosystem fit, and platform stability note on online booking clinics or groups building a booking tool exclusively for their own use are permitted to do so via the api third party online booking products intended for deployment across multiple clinics are not eligible, as this overlaps with core digitail functionality note for clinic owned builds clinics or groups using the api to build custom tools on top of their own digitail data are required to sign a data processing agreement (dpa) before production access is granted this covers how patient and clinical data is handled, stored, and protected within your custom application is the digitail api right for me? the digitail api is designed for teams that need programmatic, real time access to clinic data and are prepared to build and maintain their own integrations use the guidance below to decide whether the api is the right solution for your use case the digitail api is a good fit if you have a clear integration use case (e g syncing invoices, sending lab results, building dashboards, connecting external systems) have development resources available to build and maintain the integration are comfortable working with rest apis and oauth 2 0 need real time data access , not manual exports are building something that actively benefits digitail clinics understand that integrations are self service and independently developed the digitail api may not be the right fit if you are looking for one time data exports or ad hoc reports expect digitail to build, customize, or maintain the integration for you need bulk data operations (bulk creates or updates are not supported) do not have technical resources to implement oauth and api logic want access to all digitail clinics without individual authorization are exploring the api primarily for competitive analysis or data aggregation partnership tiers all approved integrations start at tier 0 (self serve) based on usage, strategic fit, and mutual interest, partners can progress to tier 1 or tier 2 the tier determines the level of support, visibility, and collaboration you can expect from digitail tier 0 self serve the default starting point for all approved integrations access api documentation, sandbox environment, developer portal support public documentation only — no direct support channel, no technical q\&a, no implementation calls visibility not listed in the digitail partner marketplace this tier is designed for teams that are fully independent in their development process digitail does not join implementation calls, answer architecture questions, or debug partner code at this tier most questions can be answered through the public documentation at documentation digitail io tier 1 qualified partner available to integrations that have demonstrated active usage by digitail clinics and a clear fit with the digitail ecosystem tier 1 status is reviewed and approved by digitail on a quarterly basis access everything in tier 0 support access to the api slack workspace for async support visibility listed in the digitail partner marketplace, included in relevant sales conversations how to qualify active clinic usage + strategic fit, reviewed quarterly tier 2 strategic partner reserved for integrations with significant distribution or revenue potential and a mutual commitment to a deeper partnership requires a formal agreement with digitail access everything in tier 1 support dedicated digitail contact, formal sla collaboration joint go to market, access to roadmap conversations, potential co build investment from digitail where native product embedding is required agreement formal partnership agreement required (covering ip ownership, commercial terms, sla, and termination) how to qualify by invitation or mutual agreement with digitail's cpo and revenue leader to express interest in being considered for tier 1 or tier 2, reach out to api\@digitail io with a summary of your integration, current usage, and partnership goals