Word Pronunciation API GET

Word Pronunciation is a simple tool for getting the pronunciation of a word. It returns the pronunciation of the word provided.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/wordpronunciation

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Word Pronunciation response payload
  }
}

About the Word Pronunciation API

Word Pronunciation works by analyzing the word provided and getting the pronunciation. It uses advanced algorithms to get the pronunciation of the word and returns the pronunciation.

What people use it for

Language Learning: Use the Word Pronunciation API to get word pronunciation for language learning. Use the data to learn correct pronunciation, improve language skills, and enhance communication
Speech Recognition: Get word pronunciation by using the Word Pronunciation API for speech recognition. Use the data to recognize words, transcribe speech, and enhance voice commands
Text-to-Speech: Use the Word Pronunciation API to get word pronunciation for text-to-speech. Use the data to convert text to speech, generate audio files, and enhance accessibility
Pronunciation Guide: Get word pronunciation by using the Word Pronunciation API for pronunciation guide. Use the data to create pronunciation guides, improve pronunciation, and enhance understanding

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Word Pronunciation

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets

Questions.

Common questions about the Word Pronunciation API.

Read the docs →

What does the Word Pronunciation API do?

Word Pronunciation is a simple tool for getting the pronunciation of a word. It returns the pronunciation of the word provided.

How do I authenticate Word Pronunciation API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Word Pronunciation API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Word Pronunciation API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Word Pronunciation API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Word Pronunciation API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/wordpronunciation

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`word`Required	string	`hello`	The word to get the pronunciation of

Example request

1
2

curl "https://api.apiverve.com/v1/wordpronunciation?word=hello" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/wordpronunciation

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "word": "hello",
    "pronounciation": "HH AH0 L OW1"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`word`	string	`"hello"`	The word provided for pronunciation lookup
`pronounciation`	string	`"HH AH0 L OW1"`	Phonetic pronunciation of the word in ARPAbet format

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Word Pronunciation calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/wordpronunciation

No SDK to install — this is a plain HTTPS call to /v1/wordpronunciation with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/wordpronunciation" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/wordpronunciation-apiSource, issues and the examples this page is built from.ReferenceWord Pronunciation API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/wordpronunciationnpm apiverve-wordpronunciationPyPI APIVerve.API.WordPronunciationNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/wordpronunciation

Install the Node.js SDK, then call the Word Pronunciation API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/wordpronunciation

Node.js

const res = await fetch("https://api.apiverve.com/v1/wordpronunciation", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/wordpronunciationThe published Node.js client, versioned and signed.GitHubapiverve/wordpronunciation-apiSource, issues and the examples this page is built from.ReferenceWord Pronunciation API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

apiverve-wordpronunciationPyPI APIVerve.API.WordPronunciationNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/wordpronunciation

Install the Python SDK, then call the Word Pronunciation API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — PyPI

pip install apiverve-wordpronunciation

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/wordpronunciation",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

PyPIapiverve-wordpronunciationThe published Python client, versioned and signed.GitHubapiverve/wordpronunciation-apiSource, issues and the examples this page is built from.ReferenceWord Pronunciation API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/wordpronunciationnpm APIVerve.API.WordPronunciationNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/wordpronunciation

Install the C# / .NET SDK, then call the Word Pronunciation API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.WordPronunciation

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/wordpronunciation");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.WordPronunciationThe published C# / .NET client, versioned and signed.GitHubapiverve/wordpronunciation-apiSource, issues and the examples this page is built from.ReferenceWord Pronunciation API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/wordpronunciationnpm apiverve-wordpronunciationPyPI

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/wordpronunciation

No SDK to install — this is a plain HTTPS call to /v1/wordpronunciation with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/wordpronunciation", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/wordpronunciationnpm apiverve-wordpronunciationPyPI APIVerve.API.WordPronunciationNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/wordpronunciation

No SDK to install — this is a plain HTTPS call to /v1/wordpronunciation with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/wordpronunciation");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/wordpronunciationnpm apiverve-wordpronunciationPyPI APIVerve.API.WordPronunciationNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/wordpronunciation

No SDK to install — this is a plain HTTPS call to /v1/wordpronunciation with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/wordpronunciation")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/wordpronunciationnpm apiverve-wordpronunciationPyPI APIVerve.API.WordPronunciationNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Text Processing

View all 45 →

All articles →

Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read

Summarize Text with AI: A Practical GuideUse AI to summarize articles, documents, and user content. Tutorial with code for content platforms, research tools, and dashboards.Read

7 Content Moderation Mistakes That Sink AppsYour app allows user content. Here are the moderation mistakes that get apps pulled from stores.Read

Word Pronunciation API GET

Try it — live request, no key required

About the Word Pronunciation API

What people use it for

Ways to call it

Other ways to use Word Pronunciation

Questions.

Request parameters — GET /v1/wordpronunciation

Required

Authentication

Response — GET /v1/wordpronunciation

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/wordpronunciation

Resources

Also published for

Call it from Node.js — GET /v1/wordpronunciation

Resources

Also published for

Call it from Python — GET /v1/wordpronunciation

Resources

Also published for

Call it from C# / .NET — GET /v1/wordpronunciation

Resources

Also published for

Call it from Go — GET /v1/wordpronunciation

Resources

Also published for

Call it from PHP — GET /v1/wordpronunciation

Resources

Also published for

Call it from Ruby — GET /v1/wordpronunciation

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Word Pronunciation API

Text Processing

Related articles

Ready to build with Word Pronunciation? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog