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

Dify Audio API

Text-to-Speech and Speech-to-Text operations. 2 operation(s) from the Dify Service API.

Dify Audio API is one of 19 APIs that Dify publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 2 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.0.1, at version 1.0.0.

Requests are made against a single base URL, https://{api_base_url}.

2 operations 2 paths 3 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0.0
Base URL
https://api.dify.ai/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Dify Audio API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API_KEY) (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — Every request authenticates with an API key: Authorization: Bearer {APIKEY}. App endpoints take an app API key; knowledge endpoints take a knowledge base API k…

Paths & Operations 2

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

Audio 2

Text-to-Speech and Speech-to-Text operations.

POST
/audio-to-text
Convert Audio to Text
audioToText body → 200400413415500
POST
/text-to-audio
Convert Text to Audio
textToAudioChat body → 200400500

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are TextToAudioRequest (5 properties), AudioToTextRequest (2 properties), AudioToTextResponse (1 property). Each schema is shown below with its type and property counts.

AudioToTextRequest
object
Request body for audio-to-text conversion.
2 properties 1 required
AudioToTextResponse
object
1 property
TextToAudioRequest
object
Request body for text-to-audio conversion. Provide either messageid or text.
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dify-audio-api-openapi.yml Raw ↑

Other APIs Dify publishes across the network.

Dify Chat Messages API
Dify Completion Messages API
Dify Conversations API
Dify Knowledge Bases API
Dify Files API
Dify Workflow Runs API
Dify Applications API
Dify Annotations API
Dify Feedback API
Dify End Users API
Dify Human Input API
Where this information came from

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