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

Huma Key Actions API

The Key Actions API from Huma — 6 operation(s) for key actions.

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

Tagged areas include Key Actions. 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 7 operations across 6 paths, and defines 17 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.

7 operations 6 paths 17 schemas 1 DELETE5 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 Key Actions 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 7

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

Key Actions 7
GET
/api/extensions/v1/user/{user_id}/key-action
Retrieve To Do Items For User
api_extensions_v1_user_key_action_retrieve_[retrieve_to_do_items_for_user] 4 params → 200
POST
/api/extensions/v1/user/{user_id}/key-action/{key_action_id}
Create Key Action Log
api_extensions_v1_user_key_action_create_[create_key_action_log] 2 params body → 201
DELETE
/api/extensions/v1/user/{user_id}/key-action/{key_action_id}
Delete Key Action Log
api_extensions_v1_user_key_action_destroy_[delete_key_action_log] 4 params → 204
GET
/api/extensions/v1/user/{user_id}/key-action/expiring
Retrieve Expiring Key Actions In Timeframe
api_extensions_v1_user_key_action_expiring_retrieve_[retrieve_expiring_key_actions_in_timeframe] 4 params → 200
GET
/api/extensions/v1/user/{user_id}/key-action/forms-timeline
Retrieve Grouped Forms Timeline
api_extensions_v1_user_key_action_forms_timeline_retrieve_[retrieve_grouped_forms_timeline] 3 params → 200
GET
/api/extensions/v1/user/{user_id}/key-action/grouped-forms-stats
Retrieve Grouped Forms Stats
api_extensions_v1_user_key_action_grouped_forms_stats_retrieve_[retrieve_grouped_forms_stats] 1 param → 200
GET
/api/extensions/v1/user/{user_id}/key-action/timeframe
Retrieve To Do Items In Timeframe
api_extensions_v1_user_key_action_timeframe_retrieve_[retrieve_to_do_items_in_timeframe] 4 params → 200

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are QuestionnaireDTODRF (37 properties), RetrieveToDoItemsResponseDRF (24 properties), FormDataDRF (23 properties), QuestionnaireAnswerDRF (22 properties). Each schema is shown below with its type and property counts.

QuestionnaireDTODRF
object
37 properties 7 required
FeedbackNotificationDataDRF
object
5 properties
ResultIdResponseObjectDRF
object
1 property
ServerDRF
object
3 properties 3 required
PeriodProgressResponseDRF
object
4 properties
RetrieveToDoItemsResponseDRF
object
24 properties 2 required
QuestionnaireAppResultDRF
object
2 properties 2 required
FeedbackTextDRF
object
3 properties 2 required
QuestionnaireAnswerDRF
object
22 properties 1 required
UserAgentDRF
object
10 properties 4 required
ModuleFeedbackDRF
object
5 properties
QuestionnaireAnswerMediaFileDRF
object
3 properties 2 required
QuestionnaireAppResultValueDRF
object
3 properties 3 required
CreateKeyActionLogDTORequestBodyDRF
object
5 properties 3 required
KeyActionResponseDRF
object
21 properties 2 required
FormDataDRF
object
23 properties 2 required
DeviceDetailsDRF
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

huma-key-actions-api-openapi.yml Raw ↑

Other APIs Huma publishes across the network.

Huma Mobile & Web SDK
Huma AI Engine API
Huma Appointment API
Huma Assets API
Huma Audit Log API
Huma Auth API
Huma Authorization Admin API
Huma Autocomplete API
Huma Billing API
Huma Billing Portal Route API
Huma Builder API
Huma Calendar Route API
Where this information came from

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