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

Hume AI subpackage_voices API

The subpackage_voices API from Hume AI — 1 operation(s) for subpackage_voices.

Hume AI subpackage_voices API is one of 10 APIs that Hume AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, pricing, and an AsyncAPI specification.

This API exposes 3 operations across 1 path, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.hume.ai.

3 operations 1 paths 9 schemas 1 DELETE1 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://api.hume.ai
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Hume AI subpackage_voices API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Hume-Api-Key (bearerAuth).

Paths & Operations 3

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

subpackage_voices 3
POST
/v0/tts/voices
Create voice
create 1 param body → 200422
GET
/v0/tts/voices
List voices
list 6 params → 200
DELETE
/v0/tts/voices
Delete voice
delete 2 params → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are return_voice_octave_public (4 properties), return_paged_octave_public_voices (4 properties), ValidationError (3 properties), OctaveVoiceDesignSaveResponse (3 properties). Each schema is shown below with its type and property counts.

return_paged_octave_public_voices
object
A paginated list Octave voices available for text-to-speech
4 properties 4 required
OctaveVoiceDesignSaveArgs
object
2 properties 2 required
VoiceProvider
string
return_voice_octave_public
object
An Octave voice available for text-to-speech
4 properties 3 required
HTTPValidationError
object
1 property
OctaveVoiceDesignSaveResponse
object
3 properties 3 required
ValidationError
object
3 properties 3 required
ValidationErrorLocItems
voices_delete_Response_200
object
Empty response body

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hume-ai-subpackage-voices-api-openapi.yml Raw ↑

Other APIs Hume AI publishes across the network.

Hume AI Ai Default API
Hume AI subpackage_batch API
Hume AI subpackage_chatGroups API
Hume AI subpackage_chats API
Hume AI subpackage_configs API
Hume AI subpackage_controlPlane API
Hume AI subpackage_prompts API
Hume AI subpackage_tools API
Hume AI Speech To Speech (EVI) API
Where this information came from

This is an independent, third-party profile of Hume AI subpackage_voices 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.