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

AWS HealthLake Tags API

Resource tagging operations for cost allocation and resource management

AWS HealthLake Tags API is one of 8 APIs that AWS HealthLake publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Tags. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 3 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2017-07-01.

Requests are made against a single base URL, https://healthlake.{region}.amazonaws.com.

3 operations 3 paths 6 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2017-07-01
Base URL
https://healthlake.us-east-1.amazonaws.com
Authentication
API Key
License
Terms of Service
Resource Areas
1

Authentication & Security 1

AWS HealthLake Tags API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (aws_v4). By default, every request must be authenticated.

  • aws_v4 — AWS Signature Version 4. Sign requests with your AWS access key and secret key. See: https://docs.aws.amazon.com/general/latest/gr/signingawsapirequests.html

Paths & Operations 3

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

Tags 3

Resource tagging operations for cost allocation and resource management

POST
/#X-Amz-Target=HealthLake.ListTagsForResource
ListTagsForResource
listTagsForResource 1 param body → 200400500
POST
/#X-Amz-Target=HealthLake.TagResource
TagResource
tagResource 1 param body → 200400500
POST
/#X-Amz-Target=HealthLake.UntagResource
UntagResource
untagResource 1 param body → 200400500

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are UntagResourceRequest (2 properties), TagResourceRequest (2 properties), ListTagsForResourceRequest (1 property), ListTagsForResourceResponse (1 property). Each schema is shown below with its type and property counts.

TagResourceRequest
object
2 properties 2 required
UntagResourceResponse
object
TagResourceResponse
object
ListTagsForResourceResponse
object
1 property
UntagResourceRequest
object
2 properties 2 required
ListTagsForResourceRequest
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aws-healthlake-tags-api-openapi.yml Raw ↑

Other APIs AWS HealthLake publishes across the network.

AWS HealthLake FHIR Import API
AWS HealthLake FHIR Export API
AWS HealthLake FHIR R4 Server API
AWS HealthLake Resource Tagging API
AWS HealthLake Datastore API
AWS HealthLake Export API
AWS HealthLake Import API
Where this information came from

This is an independent, third-party profile of AWS HealthLake Tags 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.