API directory · Licensed enterprise application
Nuance Dragon Copilot / DAX API
Sold as a licensed clinical application through Microsoft and its channel. Microsoft publishes licensing and security documentation but no public developer API reference.
Short answer
What does the Nuance Dragon Copilot / DAX API give a developer?
Sold as a licensed clinical application through Microsoft and its channel. Microsoft publishes licensing and security documentation but no public developer API reference.
Base URL: None published
Auth: Microsoft enterprise identity; third-party developer access is programme-gated
Cite as: Nuance Dragon Copilot / DAX API listing, Compare Healthcare API, last reviewed 2026-09-01.
Endpoints
No developer endpoints are published for third parties.
Published rate limits
Numbers the vendor states publicly. Anything unpublished should be made contractual before you plan capacity.
| Concurrency / requests per minute | Not applicable — no public API |
|---|
Published pricing
List prices as published on the vendor's own pricing page at the verification date. Follow the source link before you quote these to anyone.
| Published price | Not publicly disclosed |
|---|---|
| Licensing model | Per-user subscription plus pay-as-you-go consumption (Microsoft licensing guidance) |
| Marketplace purchase | Requires pre-purchase coordination with Microsoft; no self-serve checkout |
Data handling and compliance
The three answers a health-system security review will ask you for, as published.
| BAA | Covered by the Microsoft Products and Services Data Protection Addendum and HIPAA terms |
|---|---|
| Retention | Documented in the Dragon Copilot privacy and data-utilisation white papers |
| Training on PHI | Governed by the Microsoft DPA and service-specific terms |
How to integrate the Nuance Dragon Copilot / DAX API
An ordered path based on the public documentation, written for an engineering team scoping the work.
- 01
Read the licensing guidance
Confirm whether your customer buys per-user seats, consumption, or both — it changes your commercial model entirely.
- 02
Check EHR surface
Deployment is through EHR-embedded experiences, not an endpoint you call from your product.
- 03
Use the white papers
The security and privacy white papers are usable evidence in your customer's security review even when you are not the buyer.
What the documentation does not warn you about
The judgement an endpoint list cannot give you.
Incumbency and EHR depth are real; none of it is addressable by a software team that needs to ship a documentation feature under its own brand.
Primary sources for this listing
Every fact above traces to one of these pages. If one has changed, tell us and the listing is re-verified.
- Dragon Copilot product page https://www.microsoft.com/en-us/health-solutions/clinical-workflow/dragon-copilot
- Licensing guidance https://www.microsoft.com/licensing/guidance/Dragon-Copilot
- Security white paper https://learn.microsoft.com/en-us/industry/healthcare/dragon-copilot/whitepapers/security
- Privacy white paper https://learn.microsoft.com/en-us/industry/healthcare/dragon-copilot/whitepapers/privacy
Evidence & sources
Standards the integration steps above assume. Vendor-specific evidence is the primary source list on this page.
U.S. Department of Health & Human Services · Regulation · Tier A — primary documentation
Supports: The contractual clauses a documentation vendor's BAA must contain.
U.S. Department of Health & Human Services · Regulation · Tier A — primary documentation
Supports: Administrative, physical and technical safeguards a vendor handling recorded encounter audio must implement.
HL7 International · Standard · Tier A — primary documentation
Supports: Resource definitions (DocumentReference, Composition, Encounter, Condition, MedicationRequest) that clinical documentation output must map onto.
Source tiers are defined on the methodology page. Outbound links are unaffiliated and carry no commercial relationship.
Frequently asked questions
- Does Nuance Dragon Copilot / DAX have a public API?
- Sold as a licensed clinical application through Microsoft and its channel. Microsoft publishes licensing and security documentation but no public developer API reference.
- How do you authenticate with the Nuance Dragon Copilot / DAX API?
- Microsoft enterprise identity; third-party developer access is programme-gated
- What are the Nuance Dragon Copilot / DAX API rate limits?
- Concurrency / requests per minute: Not applicable — no public API
- How much does the Nuance Dragon Copilot / DAX API cost?
- Published price: Not publicly disclosed. Licensing model: Per-user subscription plus pay-as-you-go consumption (Microsoft licensing guidance). Marketplace purchase: Requires pre-purchase coordination with Microsoft; no self-serve checkout
- Can you evaluate Nuance Dragon Copilot / DAX without a sales conversation?
- No — purchase requires Microsoft engagement