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

LOVO AI Text-to-Speech API

Convert text to speech synchronously or asynchronously and retrieve job results.

LOVO AI Text-to-Speech API is one of 3 APIs that LOVO AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Text-to-Speech. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 10 schemas. It is described by OpenAPI 3.0.0, at version 1.0.

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

3 operations 3 paths 10 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0
Base URL
https://api.genny.lovo.ai/api/v1
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

LOVO AI Text-to-Speech API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-KEY (X-API-KEY). By default, every request must be authenticated.

  • X-API-KEY — API key generated at https://genny.lovo.ai (profile tab).

Paths & Operations 3

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

Text-to-Speech 3

Convert text to speech synchronously or asynchronously and retrieve job results.

POST
/api/v1/tts
Async TTS
async-tts body → 201400401402422
POST
/api/v1/tts/sync
Sync TTS
sync-tts body → 201400401402422
GET
/api/v1/tts/{jobId}
Async Retrieve Job
async-retrieve-job 1 param → 200400401422

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are GetJobResponse (12 properties), TextToSpeechOutput (10 properties), TextToSpeechRequest (5 properties), TextToSpeechSyncRequest (4 properties). Each schema is shown below with its type and property counts.

TextToSpeechResponse
JobErrorResponse
object
2 properties 2 required
GetJobResponse
object
12 properties 7 required
TextToSpeechSyncRequest
object
4 properties 2 required
TextToSpeechSyncResponse
Emphasis
object
An emphasis marker applied at a position within the synthesized text.
2 properties 2 required
Pronunciation
object
A word-level pronunciation override applied to a TTS conversion.
3 properties 3 required
Pause
object
A pause inserted at a position within the synthesized text.
2 properties 2 required
TextToSpeechRequest
object
5 properties 2 required
TextToSpeechOutput
object
10 properties 8 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lovo-ai-text-to-speech-api-openapi.yml Raw ↑

Other APIs LOVO AI publishes across the network.

LOVO AI Speakers API
LOVO AI Teams API
Where this information came from

This is an independent, third-party profile of LOVO AI Text-to-Speech 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.