How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Huma

Huma Kardia API

The Kardia API from Huma — 5 operation(s) for kardia.

Documentation Provider Profile APIs.io OpenAPI GitHub

Huma Kardia API is one of 77 APIs that Huma publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Kardia. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, a getting-started guide, and authentication docs.

This API exposes 5 operations across 5 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://workspace-gcp-uk.api.huma.com/api/integration/v1.

5 operations 5 paths 13 schemas 4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://workspace-gcp-uk.api.huma.com/api/integration/v1
Authentication
API Key, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 3

Huma Kardia API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (Hawk_Auth). It accepts HTTP bearer tokens (JWT) (JWT_Auth). It accepts HTTP bearer tokens (JWT) (jwtAuth).

  • Hawk_Auth — Hawk MAC authentication. Paste a full Authorization header value. Example: Authorization: Hawk id="userId:clientId", ts=" ", nonce=" ", mac=" "[, hash=" "][, e…
  • JWT_Auth — Use HTTP Bearer auth with a JWT. Send the token in the Authorization header: Authorization: Bearer The token should contain standard claims plus projectId and…

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 4 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Kardia 5
GET
/api/extensions/v1/kardia/ecg-pdf/{user_id}/{record_id}
Retrieve Single Ecg Pdf
api_extensions_v1_kardia_ecg_pdf_retrieve_[retrieve_single_ecg_pdf] 2 params → 200
GET
/api/extensions/v1/kardia/ecg/{record_id}
Retrieve Single Ecg
api_extensions_v1_kardia_ecg_retrieve_[retrieve_single_ecg] 1 param
POST
/api/extensions/v1/kardia/patient/{user_id}
Create Kardia Patient
api_extensions_v1_kardia_patient_create_[create_kardia_patient] 1 param body → 200
GET
/api/extensions/v1/kardia/recordings/{patient_id}
Retrieve Patient Recordings
api_extensions_v1_kardia_recordings_retrieve_[retrieve_patient_recordings] 1 param → 200
GET
/api/extensions/v1/kardia/sync/{user_id}
Sync Kardia Data
api_extensions_v1_kardia_sync_retrieve_[sync_kardia_data] 1 param → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are ECGAliveCorDTODRF (28 properties), UserAgentDRF (10 properties), CreateKardiaPatientResponseDRF (8 properties), PatientRecordingDRF (7 properties). Each schema is shown below with its type and property counts.

ECGAliveCorDTODRF
object
28 properties 6 required
FeedbackNotificationDataDRF
object
5 properties
CreateKardiaPatientRequestBodyDRF
object
2 properties 2 required
ServerDRF
object
3 properties 3 required
S3ObjectDRF
object
3 properties 2 required
CreateKardiaPatientResponseDRF
object
8 properties
PatientRecordingPageInfoDRF
object
3 properties
PatientRecordingDRF
object
7 properties
FeedbackTextDRF
object
3 properties 2 required
RetrievePatientRecordingResponseDRF
object
3 properties
UserAgentDRF
object
10 properties 4 required
ModuleFeedbackDRF
object
5 properties
DeviceDetailsDRF
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

huma-kardia-api-openapi.yml Raw ↑

Other APIs Huma publishes across the network.

Huma Mobile & Web SDK
AE Profile APIs.io
Huma AI Engine API
AE Profile APIs.io
Huma Appointment API
AE Profile APIs.io
Huma Assets API
AE Profile APIs.io
Huma Audit Log API
AE Profile APIs.io
Huma Auth API
AE Profile APIs.io
Huma Authorization Admin API
AE Profile APIs.io
Huma Autocomplete API
AE Profile APIs.io
Huma Billing API
AE Profile APIs.io
Huma Billing Portal Route API
AE Profile APIs.io
Huma Builder API
AE Profile APIs.io
Huma Calendar Route API
AE Profile APIs.io
#Kardia
← Back to H APIs
API Details
ID
huma:huma-kardia-api
Base URL
https://workspace-gcp-uk.api.huma.com/api/integration/v1
Docs
https://docs.huma.com/api-integration/intro
Provider
Huma
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=huma-kardia-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/huma-kardia-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Huma Kardia API, 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.