tab32
tab32 is a cloud-based dental practice management, imaging, and analytics platform for dental practices and dental service organizations (DSOs). tab32 offers a real, commercial API - powered by Google Apigee and HIPAA / SOC 2 Type II compliant - that exposes tab32's patient, provider, schedule, charts, notes, ledger, and payments data objects to DSOs and third-party developers. Access is partner-gated, not open self-service - developers reach the API through tab32's developer API portal after establishing a partnership or enterprise relationship, and full endpoint reference, authentication, and base URL details live behind that portal rather than on the public website. The API entries below are modeled from tab32's publicly documented data objects and API messaging; their endpoint paths are not published publicly and are therefore illustrative, not confirmed.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles tab32 the way a machine reads it — 9 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — tab32 scores 11.1/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from tab32's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tab32/"
title="tab32 on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tab32.svg"
alt="tab32 Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/tab32/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tab32/"
title="tab32 on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tab32/card.svg"
alt="tab32 Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile tab32
Each block below is one kind of artifact we hold for tab32. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
tab32 Patients API
Access to the tab32 patient data object - demographics, contact and insurance details, and patient records - for integrating patient management into CRM, patient-facing apps, an...
tab32 Providers API
Access to the tab32 provider data object - dentists, hygienists, and other practitioners across a practice or DSO's locations. Endpoint paths are not published publicly; access ...
tab32 Schedule API
Access to the tab32 schedule data object - appointments, availability, and booking - supporting online booking, recall, and appointment-scheduling integrations. Endpoint paths a...
tab32 Charts API
Access to the tab32 charts data object - clinical and periodontal charting and treatment planning data - for clinical workflow and analytics integrations. Endpoint paths are not...
tab32 Notes API
Access to the tab32 notes data object - clinical and progress notes attached to patient and encounter records. Endpoint paths are not published publicly; access is via the partn...
tab32 Ledger API
Access to the tab32 ledger data object - patient and practice financial ledger, charges, and insurance claim / revenue-cycle data. Endpoint paths are not published publicly; acc...
tab32 Payments API
Access to the tab32 payments data object - patient payments and transaction records (tab32 integrates payment processing via Stripe). Endpoint paths are not published publicly; ...
Scroll within the panel for all 7 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Tab32 Plans Pricing
PLANSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for tab32 — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Access & Security 1
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/tab32 · machine-readable index on apis.io
This is an independent, third-party profile of tab32, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.