Words to Numbers is a simple tool for converting words to numbers. It returns the words in numbers.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Words to Numbers response payload
}
}
About the Words to Numbers API
Words to Numbers works by converting words to numbers using a predefined set of rules. It supports a wide range of words and provides the equivalent numbers in a structured format.
What people use it for
- Financial Applications
- Use the Words to Numbers API to convert words to numbers in financial applications. Use the data to process checks, invoices, and receipts
- Educational Tools
- Develop educational tools by using the Words to Numbers API to convert words to numbers. Use the data to teach students about number systems and language
- Document Processing
- Process documents by using the Words to Numbers API to convert words to numbers. Use the data to automate data entry and improve accuracy in reports and forms
- Game Development
- Develop games by using the Words to Numbers API to convert words to numbers. Use the data to create puzzles, challenges, and interactive activities
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
Other ways to use Words to Numbers
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Words to Numbers API do?
How do I authenticate Words to Numbers API requests?
How much does the Words to Numbers API cost?
How fast is the Words to Numbers API?
What response formats does the Words to Numbers API support?
What HTTP method does the Words to Numbers API use?
Request parameters — GET /v1/wordstonumbers
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 |
|---|---|---|---|
wordsRequired | string | seven thousand six hundred and twenty | The words to convert to numbers |
curl "https://api.apiverve.com/v1/wordstonumbers?words=seven%20thousand%20six%20hundred%20and%20twenty" \
-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-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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/wordstonumbers
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.
{
"status": "ok",
"error": null,
"data": {
"number": "7620",
"words": "seven thousand, six hundred twenty",
"ordinal": "seven thousand, six hundred twentieth",
"numberOfDigits_numeric": 4,
"numberOfDigits_words": "four",
"eachNumber": [
"seven",
"six",
"two",
"zero"
]
}
}
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 |
|---|---|---|---|
number | string | "7620" | Numeric representation of the input words |
words | string | "seven thousand, six hundred twenty" | Original words formatted in standard English notation |
ordinalPremium | string | "seven thousand, six hundred twentieth" | Ordinal form of the number in words |
numberOfDigits_numeric | number | 4 | Count of individual digits in the number |
numberOfDigits_words | string | "four" | Digit count expressed in words format |
eachNumberPremium | array | [seven, ...] | Array with each digit represented as a word |
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 cycle's allowance |
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 | Words to Numbers 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.
Call it from cURL — GET /v1/wordstonumbers
No SDK to install — this is a plain HTTPS call to /v1/wordstonumbers with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/wordstonumbers" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
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/wordstonumbers
Install the Node.js SDK, then call the Words to Numbers API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/wordstonumbersconst res = await fetch("https://api.apiverve.com/v1/wordstonumbers", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/wordstonumbers
Install the Python SDK, then call the Words to Numbers API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-wordstonumbersimport requests
res = requests.get(
"https://api.apiverve.com/v1/wordstonumbers",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
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/wordstonumbers
Install the C# / .NET SDK, then call the Words to Numbers API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.WordstoNumbersusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/wordstonumbers");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/wordstonumbers
No SDK to install — this is a plain HTTPS call to /v1/wordstonumbers 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/wordstonumbers", 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
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/wordstonumbers
No SDK to install — this is a plain HTTPS call to /v1/wordstonumbers with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/wordstonumbers");
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
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/wordstonumbers
No SDK to install — this is a plain HTTPS call to /v1/wordstonumbers with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/wordstonumbers")
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.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Words to Numbers form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Words to Numbers API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog.
Data Conversion
- ASCII85 Encoder
- Base64 Encoder/Decoder
- Color Converter
- CSV to JSON Converter
- File Size Formatter
- HTML Entities Encoder/Decoder
- HTML to Image
- JSON to CSV Converter
- JSON to JSONP
- JWT Decoder
- Markdown Table Generator
- Markdown to HTML
- Markdown to Image
- Markdown to PDF
- Math Calculator
- Meeting Time Converter
- Number Base Converter
- Number to Words
- Placeholder Text Generator
- Punycode Converter
- Query String Builder
- Relative Time Formatter
- Roman Numeral Converter
- Text to Color
- Unicode Escape/Unescape
- Unit Converter
- Unix Timestamp Converter
- URL Encoder/Decoder
- URL to Markdown
- Variable Name Converter
- Website to Text
- Words to Numbers
- XML to JSON
Related articles
All articles →
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read
Generate PDFs from HTML with an APIConvert HTML to PDF programmatically. Tutorial covering invoices, reports, receipts, and certificates with code examples.Read
Automating Visual Testing With ScreenshotsCatch visual bugs before users do. Here's how to add screenshot-based testing to your workflow.Read