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

The CMS API from Huma — 10 operation(s) for cms.

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

Tagged areas include CMS. 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 12 operations across 10 paths, and defines 12 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.

12 operations 10 paths 12 schemas 1 DELETE6 GET4 POST1 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 CMS 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 12

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

CMS 12
POST
/api/extensions/v1/cms/{collection}
Create Content
api_extensions_v1_cms_create_[create_content] 1 param body → 201
GET
/api/extensions/v1/cms/{collection}/{content_id}
Retrieve Content
api_extensions_v1_cms_retrieve_[retrieve_content] 4 params → 200
PUT
/api/extensions/v1/cms/{collection}/{content_id}
Update Content
api_extensions_v1_cms_update_[update_content] 2 params body → 200
DELETE
/api/extensions/v1/cms/{collection}/{content_id}
Delete Content
api_extensions_v1_cms_destroy_[delete_content] 4 params → 204
GET
/api/extensions/v1/cms/{collection}/{content_id}/{version}
Retrieve Content Version
api_extensions_v1_cms_retrieve_[retrieve_content_version] 5 params → 200
POST
/api/extensions/v1/cms/{collection}/{content_id}/publish
Publish Draft
api_extensions_v1_cms_publish_create_[publish_draft] 5 params → 201
GET
/api/extensions/v1/cms/{collection}/schema
Retrieve Schema
api_extensions_v1_cms_schema_retrieve_[retrieve_schema] 1 param → 200
POST
/api/extensions/v1/cms/{collection}/search
Search Content
api_extensions_v1_cms_search_create_[search_content] 1 param body → 200
GET
/api/extensions/v1/cms/{collection}/tags
Retrieve Collection Tags
api_extensions_v1_cms_tags_retrieve_[retrieve_collection_tags] 1 param → 200
GET
/api/extensions/v1/cms/collections
List Collections
api_extensions_v1_cms_collections_retrieve_[list_collections] → 200
GET
/api/extensions/v1/public_cms/{collection}/{content_id}
Retrieve Content
api_extensions_v1_public_cms_retrieve_[retrieve_content] 4 params → 200
POST
/api/extensions/v1/public_cms/{collection}/search
Search Content
api_extensions_v1_public_cms_search_create_[search_content] 1 param body → 200

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are CMSContentDTODRF (14 properties), CreateContentRequestObjectDRF (14 properties), UpdateContentRequestObjectDRF (14 properties), SearchContentRequestObjectDRF (7 properties). Each schema is shown below with its type and property counts.

PublicContentSearchResponseObjectDRF
object
4 properties
SearchContentResponseObjectDRF
object
4 properties
ResultIdResponseObjectDRF
object
1 property
SearchContentRequestObjectDRF
object
7 properties 1 required
SortFieldDRF
object
2 properties 2 required
UpdateContentRequestObjectDRF
object
14 properties 2 required
CreateContentResponseObjectDRF
object
1 property 1 required
CreateContentRequestObjectDRF
object
14 properties 3 required
CMSContentDTODRF
object
14 properties 3 required
ListCollectionsResponseDRF
object
1 property 1 required
TagsListResponseDRF
object
1 property 1 required
RetrieveSchemaResponseDRF
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

huma-cms-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 CMS 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.