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

H2O.ai Tags API

The Tags API from H2O.ai — 3 operation(s) for tags.

H2O.ai Tags API is one of 26 APIs that H2O.ai 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, API documentation, an API reference, a getting-started guide, authentication docs, and a changelog.

This API exposes 6 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version v1.0.0.

Requests are made against a single base URL, https://h2ogpte.genai.h2o.ai/api/v1.

6 operations 3 paths 6 schemas 1 DELETE3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1.0.0
Base URL
https://h2ogpte.genai.h2o.ai/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

H2O.ai Tags API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Using an API key generated by H2OGPTe

Paths & Operations 6

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

Tags 6
POST
/tags
Creates a new tag.
create_tag body → 201400401404default
GET
/tags
List tags.
list_tags → 200400401default
GET
/tags/{tag_name}
Finds a tag by its name.
get_tag 1 param → 200400401404default
DELETE
/tags/{tag_name}
Deletes a tag.
delete_tag 1 param → 200401404default
PATCH
/tags/{tag_name}
Updates attributes of a tag.
update_tag 1 param body → 200400401404default
GET
/tags/{tag_names}/documents
List documents associated with a tag.
list_documents_for_tags 2 params → 200400401default

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Document (18 properties), Tag (4 properties), EndpointError (2 properties), TagUpdateRequest (2 properties). Each schema is shown below with its type and property counts.

TagCreateRequest
object
1 property 1 required
Metadata
object
Document
object
18 properties 9 required
Tag
object
4 properties 2 required
TagUpdateRequest
object
2 properties
EndpointError
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

h2o-ai-tags-api-openapi.yml Raw ↑

Other APIs H2O.ai publishes across the network.

h2oGPTe MCP Server
H2O.ai Admin Sessions API
H2O.ai Agents API
H2O.ai AI Assistants API
H2O.ai API Keys API
H2O.ai Chat API
H2O.ai Collections API
H2O.ai Configurations API
H2O.ai Document Ingestion API
H2O.ai Documents API
H2O.ai Extractors API
H2O.ai Forums API
Where this information came from

This is an independent, third-party profile of H2O.ai 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.