HeartFlow website screenshot

HeartFlow

Heartflow, Inc. (Nasdaq: HTFL) is a healthcare technology company founded in 2010 and headquartered in San Francisco, California. Its Heartflow One platform applies AI to coronary computed tomography angiography (CCTA) to non-invasively diagnose and manage coronary artery disease, bundling Roadmap Analysis, FFRct Analysis, Plaque Analysis, Plaque Staging and the PCI Navigator, and delivering results back into hospital PACS and EMR systems. More than 650,000 patients have been analyzed across 1,800+ institutions. Heartflow runs a production REST API at api.heartflow.net and customer documentation at docs.heartflow.net, but both are authenticated: there is no public developer program, no published OpenAPI, and no self-serve signup.

HeartFlow publishes 1 API on the APIs.io network. Tagged areas include Company, Healthcare, Medical Imaging, Artificial Intelligence, and Cardiology.

HeartFlow’s developer surface includes support, engineering blog, and 14 more developer resources.

21.2/100 emerging ▬ flat Agent 3/100 human only saas Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0
AccessOpen
1 APIs
CompanyHealthcareMedical ImagingArtificial IntelligenceCardiologyDiagnosticsMedical DevicesRadiologyClinical Decision SupportMachine-Learning

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0
Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/heartflow: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Heartflow One Platform API

Production REST API behind the Heartflow One platform, observed live at https://api.heartflow.net. Every probed route answers with the Django REST Framework challenge {"detail":...

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Heartflow Rate Limits

0 limits

RATE LIMITS

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Heartflow Authentication

0 schemes

SECURITY

Heartflow Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Heartflow Trust Center

SOC 2 Type 2, ISO/IEC 27001:2022, ISO 13485:2016, HITRUST, HIPAA, GDPR, CCPA

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: heartflow
name: HeartFlow
description: 'Heartflow, Inc. (Nasdaq: HTFL) is a healthcare technology company founded in 2010 and headquartered in San Francisco,
  California. Its Heartflow One platform applies AI to coronary computed tomography angiography (CCTA) to non-invasively diagnose
  and manage coronary artery disease, bundling Roadmap Analysis, FFRct Analysis, Plaque Analysis, Plaque Staging and the PCI
  Navigator, and delivering results back into hospital PACS and EMR systems. More than 650,000 patients have been analyzed
  across 1,800+ institutions. Heartflow runs a production REST API at api.heartflow.net and customer documentation at docs.heartflow.net,
  but both are authenticated: there is no public developer program, no published OpenAPI, and no self-serve signup.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  label: Open access
  confidence: medium
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-09-02'
  method: derived
image: https://www.heartflow.com/wp-content/uploads/2025/01/heartflow_logo_white.svg
url: https://raw.githubusercontent.com/api-evangelist/heartflow/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-22'
modified: '2026-08-22'
tags:
- Company
- Healthcare
- Medical Imaging
- Artificial Intelligence
- Cardiology
- Diagnostics
- Medical Devices
- Radiology
- Clinical Decision Support
- Machine-Learning
tags_raw:
- Company
- Healthcare
- Medical Imaging
- Artificial Intelligence
- Cardiology
- Diagnostics
- Medical Devices
- Radiology
- Clinical Decision Support
- Machine Learning
apis:
- name: Heartflow One Platform API
  description: Production REST API behind the Heartflow One platform, observed live at https://api.heartflow.net. Every probed
    route answers with the Django REST Framework challenge {"detail":"Authentication credentials were not provided."}, and
    the interactive reference surfaces the framework normally exposes (/swagger/, /redoc/) return 403 rather than a public
    document. No OpenAPI or Swagger definition is retrievable without credentials, so this entry records the surface, not
    its contract.
  humanURL: https://www.heartflow.com/heartflow-one/support/
  baseURL: https://api.heartflow.net
  tags:
  - Healthcare
  - Medical Imaging
  - Cardiology
  properties: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: TrustCenter
  url: security/heartflow-trust-center.yml
- type: DomainSecurity
  url: security/heartflow-domain-security.yml
- type: Website
  url: https://www.heartflow.com/
- type: Support
  url: https://www.heartflow.com/heartflow-one/support/
- type: Blog
  url: https://www.heartflow.com/insights/
- type: GitHubOrganization
  url: https://github.com/HeartFlow
- type: Login
  url: https://app.heartflow.net/
- type: TermsOfService
  url: https://www.heartflow.com/terms-of-use/
- type: PrivacyPolicy
  url: https://www.heartflow.com/privacy-policy/
- type: Compliance
  url: conformance/heartflow-conformance.yml
- type: Conformance
  url: conformance/heartflow-conformance.yml
- type: Plans
  url: plans/heartflow-plans-pricing.yml
- type: RateLimits
  url: rate-limits/heartflow-rate-limits.yml
- type: Packages
  url: packages/heartflow-packages.yml
- type: LLMsTxt
  url: llms/heartflow-llms.txt
- type: Lifecycle
  url: lifecycle/heartflow-lifecycle.yml
x-enrichment:
  date: '2026-08-22'
  status: minimal
  artifacts_added: 11
  pass: local-v1
x-coverage:
  state: gated
  reason: customer-only-docs
  detail: Heartflow runs a live Django REST Framework API at api.heartflow.net whose every route, including the mounted /swagger/
    and /redoc/ reference pages, answers 403 "Authentication credentials were not provided.", and its documentation host docs.heartflow.net
    is a CloudFront distribution gated by signed cookies that returns 403 MissingKey on every path, so the contract exists
    but is issued only to contracted institutional customers.
  evidence:
  - url: https://api.heartflow.net/api/v1/
    status: 403
  - url: https://api.heartflow.net/swagger/
    status: 403
  - url: https://docs.heartflow.net/openapi.json
    status: 403
  - url: https://api.heartflow.net/openapi.json
    status: 404
  - url: https://www.heartflow.com/llms.txt
    status: 404
  checked: '2026-08-22'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/heartflow"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/heartflow/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/heartflow/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.