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

Inworld AI Voices API

Voice cloning, design, and lifecycle.

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

This API exposes 1 JSON Schema definition.

Tagged areas include Voices. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, an AsyncAPI specification, a JSON-LD context, and 1 JSON Schema.

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

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

7 operations 5 paths 7 schemas 1 DELETE2 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Server
https://api.inworld.ai
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Inworld AI Voices API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

Paths & Operations 7

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

Voices 7

Voice cloning, design, and lifecycle.

GET
/voices/v1/voices
List Voices
listVoices 2 params → 2004XX
POST
/voices/v1/voices:clone
Clone Voice
cloneVoice body → 2004XX
POST
/voices/v1/voices:design
Design Voice
designVoice body → 2004XX
POST
/voices/v1/voices:publish
Publish Voice
publishVoice body → 2004XX
GET
/voices/v1/voices/{voiceId}
Get Voice
getVoice 1 param → 2004XX
PATCH
/voices/v1/voices/{voiceId}
Update Voice
updateVoice 1 param body → 2004XX
DELETE
/voices/v1/voices/{voiceId}
Delete Voice
deleteVoice 1 param → 2044XX

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Voice (7 properties), CloneVoiceRequest (6 properties), DesignVoiceRequest (4 properties), UpdateVoiceRequest (3 properties). Each schema is shown below with its type and property counts.

UpdateVoiceRequest
object
3 properties
DesignVoiceRequest
object
4 properties 3 required
Error
object
2 properties
Voice
object
7 properties
CloneVoiceRequest
object
6 properties 3 required
ListVoicesResponse
object
2 properties
CloneVoiceResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

inworld-ai-voices-api-openapi.yml Raw ↑

Other APIs Inworld AI publishes across the network.

Inworld AI Models API
Inworld AI Realtime API
Inworld AI Speech To Text API
Inworld AI Text To Speech API
Inworld AI Chat Completions API
Inworld AI Routers API
Where this information came from

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