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 Organization API

The Organization API from Huma — 15 operation(s) for organization.

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

Tagged areas include Organization. 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 17 operations across 15 paths, and defines 42 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.

17 operations 15 paths 42 schemas 2 DELETE1 GET9 POST5 PUT

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 Organization 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 17

Across 15 paths, the API surfaces 17 operations — 2 DELETE, 1 GET, 9 POST, 5 PUT. Each is listed below with its method, path, parameters, and response codes.

Organization 17
POST
/api/extensions/v1/organization
Create Organization
api_extensions_v1_organization_create_[create_organization] body → 201
GET
/api/extensions/v1/organization/{organization_id}
Retrieve Organization
api_extensions_v1_organization_retrieve_[retrieve_organization] 1 param → 200
PUT
/api/extensions/v1/organization/{organization_id}
Update Organization
api_extensions_v1_organization_update_[update_organization] 1 param body → 200
DELETE
/api/extensions/v1/organization/{organization_id}
Delete Organization
api_extensions_v1_organization_destroy_[delete_organization] 1 param → 204
DELETE
/api/extensions/v1/organization/{organization_id}/deployment/{deployment_id}
Unlink Deployment
api_extensions_v1_organization_deployment_destroy_[unlink_deployment] 2 params → 204
PUT
/api/extensions/v1/organization/{organization_id}/deployment/{deployment_id}/add-econsent/{econsent_id}
Add Econsent To Deployment
api_extensions_v1_organization_deployment_add_econsent_update_[add_econsent_to_deployment] 3 params → 200
POST
/api/extensions/v1/organization/{organization_id}/econsent
Create Econsent
api_extensions_v1_organization_econsent_create_[create_econsent] 1 param body → 201
POST
/api/extensions/v1/organization/{organization_id}/econsent-forms
Retrieve Econsent Forms
api_extensions_v1_organization_econsent_forms_create_[retrieve_econsent_forms] 1 param body → 200
POST
/api/extensions/v1/organization/{organization_id}/econsent-forms/{econsent_id}
Retrieve Econsents Forms By Id
api_extensions_v1_organization_econsent_forms_create_[retrieve_econsents_forms_by_id] 2 params body → 200
PUT
/api/extensions/v1/organization/{organization_id}/econsent/{config_id}
Apply Econsent Action
api_extensions_v1_organization_econsent_update_[apply_econsent_action] 2 params body → 200
PUT
/api/extensions/v1/organization/{organization_id}/econsent/{config_id}/state/{state}
Edit Econsent State
api_extensions_v1_organization_econsent_state_update_[edit_econsent_state] 3 params → 200
POST
/api/extensions/v1/organization/{organization_id}/link-deploymentdeprecated
Link Deployment
api_extensions_v1_organization_link_deployment_create_[link_deployment] 1 param
POST
/api/extensions/v1/organization/{organization_id}/link-deployments
Link Deployments
api_extensions_v1_organization_link_deployments_create_[link_deployments] 1 param body → 200
PUT
/api/extensions/v1/organization/{organization_id}/role
Create Or Update Organization Roles
api_extensions_v1_organization_role_update_[create_or_update_organization_roles] 1 param body → 200
POST
/api/extensions/v1/organization/{organization_id}/unlink-deployments
Unlink Deployments
api_extensions_v1_organization_unlink_deployments_create_[unlink_deployments] 1 param body → 200
POST
/api/extensions/v1/organization/clone
Clone Organization
api_extensions_v1_organization_clone_create_[clone_organization] 1 param body → 201
POST
/api/extensions/v1/organization/search
Retrieve Organizations
api_extensions_v1_organization_search_create_[retrieve_organizations] body → 200

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are FeaturesDRF (30 properties), OrganizationWithExtrasDRF (26 properties), OrganizationDTODRF (24 properties), UpdateOrganizationDTORequestBodyDRF (20 properties). Each schema is shown below with its type and property counts.

EConsentSectionDRF
object
11 properties 2 required
AdditionalConsentQuestionDRF
object
7 properties 4 required
OffBoardingReasonsDRF
object
2 properties
OrganizationDTODRF
object
24 properties
PaginatedRequestBodyDRF
object
2 properties
ConsentSectionOptionsDRF
object
5 properties 2 required
MessagingDRF
object
5 properties
ReasonDRF
object
3 properties 2 required
EmailConfigDRF
object
2 properties
RoleDTODRF
object
5 properties
FeaturesDRF
object
30 properties
EConsentFormDRF
object
6 properties 6 required
SsoDRF
object
3 properties
SsoInfoDRF
object
16 properties 4 required
EmailTemplateDRF
object
3 properties 2 required
PatientPersonalizationDRF
object
2 properties
SurgeryDateRuleDRF
object
2 properties
CreateEConsentResponseObjectDRF
object
2 properties
ListIdResponseObjectDRF
object
1 property
DeploymentInfoDRF
object
5 properties 2 required
ConsentReviewDRF
object
3 properties 2 required
ResultIdResponseObjectDRF
object
1 property
OrganizationRoleUpdateRequestBodyDRF
object
1 property 1 required
MoveUserReasonsDRF
object
2 properties
SortFieldDRF
object
2 properties 2 required
AuthorisedRepDRF
object
4 properties 4 required
RetrieveEConsentsResponseObjectDRF
object
4 properties
CreateEConsentRequestBodyDRF
object
17 properties 6 required
LinkUnlinkDeploymentsRequestBodyDRF
object
1 property 1 required
S3ObjectDRF
object
3 properties 2 required
UpdateOrganizationDTORequestBodyDRF
object
20 properties
SummaryReportDRF
object
1 property
RetrieveOrganizationsRequestObjectDRF
object
6 properties 2 required
RetrieveOrganizationsResponseObjectDRF
object
4 properties
CloneOrganizationRequestBodyDRF
object
3 properties 3 required
DeviceIntegrationDRF
object
1 property
ApplyEConsentActionRequestBodyDRF
object
18 properties 7 required
ConsentSignatureDRF
object
7 properties 4 required
CreateOrganizationDTORequestBodyDRF
object
18 properties 1 required
IntercomSettingsDRF
object
4 properties
OrganizationWithExtrasDRF
object
26 properties
CloneOrganizationResponseObjectDRF
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

huma-organization-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 Organization 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.