Number to Text Pro API

Convert numbers to perfectly formatted text across 28 languages and over 35 predefined currencies. Our API handles standard, formal, and check writing formats with support for custom currencies. Perfect for financial documents, legal contracts, invoices, and multilingual applications. Simple integration with comprehensive documentation.

Number to Text Pro API Documentation

The Number to Text Pro API converts numerical values into their textual representations, supporting a wide range of languages, formatting styles, and currencies. This documentation outlines the key parameters—languageCode, formatStyle, and currencyCode—including their possible values, to ensure proper usage.

 

API Endpoint

  • URL: https://zylalabs.com/api-marketplace/tools+%26+utilities/number+to+text+pro+api/6348
  • Methods: POST, GET

1. languageCode

  • Description: Specifies the language for the text conversion.
  • Type: String
  • Required: Yes
  • Possible Values: The API supports over 35 languages. Below is the complete list of available language codes:
    • en - English (Dialects: US, UK, AU, CA, IN)
    • es - Spanish
    • fr - French
    • de - German
    • it - Italian
    • pt - Portuguese
    • nl - Dutch
    • ru - Russian
    • ar - Arabic (Dialects: EG, SA, AE, MA)
    • zh - Chinese
    • ja - Japanese
    • ko - Korean
    • hi - Hindi
    • tr - Turkish
    • pl - Polish
    • sv - Swedish
    • no - Norwegian
    • da - Danish
    • fi - Finnish
    • el - Greek
    • cs - Czech
    • hu - Hungarian
    • ro - Romanian
    • th - Thai
    • vi - Vietnamese
    • id - Indonesian
    • ms - Malay
    • he - Hebrew
    • uk - Ukrainian
    • bg - Bulgarian
    • hr - Croatian
    • sr - Serbian
    • sk - Slovak
    • sl - Slovenian
    • lt - Lithuanian
    • lv - Latvian
    • et - Estonian
    • is - Icelandic
  • Usage Note: For English (en) dialects can be specified (e.g., US for American English, GB for Britsh English and IN for Indian English). Other languages do not require dialect specification in this context.

2. formatStyle

  • Description: Defines the formatting style for the text output.
  • Type: String
  • Required: No (optional)
  • Possible Values:
    • standard - Default text representation (e.g., "one hundred twenty-three").
    • check - Format suitable for financial checks (e.g., "one hundred twenty-three and 00/100").
    • legal - Formal legal format (e.g., "One Hundred Twenty-Three").
  • Usage Note: If omitted, the API defaults to standard.

3. currencyCode

  • Description: Specifies the currency for formatting monetary values.
  • Type: String
  • Required: No (optional)
  • Possible Values: The API supports over 40 currencies. Below are the most commonly used codes:
    • USD - US Dollar ($)
    • EUR - Euro (€)
    • GBP - British Pound (£)
    • JPY - Japanese Yen (¥)
    • CAD - Canadian Dollar (C$)
    • AUD - Australian Dollar (A$)
    • CHF - Swiss Franc (Fr)
    • CNY - Chinese Yuan (¥)
    • INR - Indian Rupee (₹)
    • BRL - Brazilian Real (R$)
    • RUB - Russian Ruble (₽)
    • KRW - South Korean Won (₩)
    • MXN - Mexican Peso (Mex$)
    • SGD - Singapore Dollar (S$)
    • HKD - Hong Kong Dollar (HK$)
    • SEK - Swedish Krona (kr)
    • NOK - Norwegian Krone (kr)
    • DKK - Danish Krone (kr)
    • PLN - Polish Złoty (zł)
    • TRY - Turkish Lira (₺)
    • (Additional currencies available)
  • Usage Note: Custom currencies are also supported. If no currency is specified, the API processes the number without currency formatting.

Example Requests

Example 1: English, Standard Format

  • Request:
    GET /api?value=12345678.90&languageCode=en&currenyCode=USD&dialect=US&formatStyle=standard
  • Response:
    "twelve million three hundred forty-five thousand six hundred seventy-eight dollars and ninety cents"

Example 2: English, Check Format

  • Request:
    GET /api?value=12345678.90&languageCode=en&currenyCode=USD&dialect=US&formatStyle=check
  • Response:
    "Twelve million three hundred forty-five thousand six hundred seventy-eight dollars and 90/100 cents"

Example 3: Arabic, Standard Format, local currency

  • Request:
    POST /api
    {
        "number": 12345678.90,
        "languageCode": "ar",
        "dialect": "",
        "formatStyle": "standard",
        "currencyCode": "EGP"
    }
  • Response:
    "اثنا عشر مليون و ثلاثمائة خمسة و أربعون ألف و ستمائة ثمان و سبعون جنيه مصري و تسعون قرش"

API Documentation

Endpoints


PostNumberToText (POST)

This endpoint converts a numerical value to its textual representation using a JSON payload in the request body. It supports extensive customization for languages, currencies, dialects, and format styles. To ensure correct usage and prevent errors, use the parameter values specified below:

  • languageCode: Sets the language for conversion. Available values include "en" (English), "es" (Spanish), "fr" (French), "de" (German), "it" (Italian), "pt" (Portuguese), "nl" (Dutch), "ru" (Russian), "ar" (Arabic), "zh" (Chinese), "ja" (Japanese), "ko" (Korean), "hi" (Hindi), and over 20 others.
  • dialect: Specifies regional variations for the language. Available values depend on languageCode, e.g., for "en": "US", "UK", and "IN"; for  Arabic "ar": "EG", "SA", and "AE".
  • currencyCode: Defines the currency for monetary conversions. Available values include "USD" (US Dollar), "EUR" (Euro), "GBP" (British Pound), "JPY" (Japanese Yen), "CAD" (Canadian Dollar), "AUD" (Australian Dollar), "CHF" (Swiss Franc), "CNY" (Chinese Yuan), "INR" (Indian Rupee), and over 30 others.
  • formatStyle: Sets the output style. Available values are "standard" (e.g., "one hundred twenty-three") and "check" (e.g., "one hundred twenty-three and 00/100"), and "formal" for legal documents

Provide these parameters in the JSON payload to ensure accurate results and avoid errors. Example payload: {"value": 123.45, "languageCode": "en", "dialect": "US", "currencyCode": "USD", "formatStyle": "standard"}.

Parameters

Parameter Type Required Available Values
value Number Yes Any numerical value (e.g., 123.45)
languageCode String Yes "en", "es", "fr", "de", "it", "pt", "nl", "ru", "ar", "zh", "ja", "ko", "hi", etc. (35+ total)
dialect String Yes Depends on languageCode, e.g., "US", "UK", "AU" for "en"; "ES", "MX" for "es".
currencyCode String No "USD", "EUR", "GBP", "JPY", "CAD", "AUD", "CHF", "CNY", "INR", etc. (40+ total)
formatStyle String No "standard", "check", and "formal"
debug Boolean No true, false


                                                                            
POST https://zylalabs.com/api/6348/number+to+text+pro+api/9088/postnumbertotext
                                                                            
                                                                        

PostNumberToText - Endpoint Features

Object Description
Request Body [Required] Json
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            twelve million three hundred forty-five thousand six hundred seventy-eight dollars and ninety cents
                                                                                                                                                                                                                    
                                                                                                    

PostNumberToText - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/6348/number+to+text+pro+api/9088/postnumbertotext' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '{
  "value": 100,
  "languageCode": "en",
  "dialect": "",
  "options": {
    "formatStyle": "check"
  },
  "currencyCode": "eur"
}'

    

GetNumberToText (GET)

This endpoint converts a numerical value to its textual representation using query parameters. It supports a wide range of languages, currencies, dialects, and format styles to customize the output. To prevent errors, use the parameter values specified below:

  • languageCode: Specifies the language for conversion. Available values include "en" (English), "es" (Spanish), "fr" (French), "de" (German), "it" (Italian), "pt" (Portuguese), "nl" (Dutch), "ru" (Russian), "ar" (Arabic), "zh" (Chinese), "ja" (Japanese), "ko" (Korean), "hi" (Hindi), and over 20 others.
  • dialect: Defines regional variations for the language. Available values depend on languageCode, e.g., for "en": "US", "UK",  and "IN"; for Arabic "ar": "EG", "SA", "AE".
  • currencyCode: Specifies the currency for monetary conversions. Available values include "USD" (US Dollar), "EUR" (Euro), "GBP" (British Pound), "JPY" (Japanese Yen), "CAD" (Canadian Dollar), "AUD" (Australian Dollar), "CHF" (Swiss Franc), "CNY" (Chinese Yuan), "INR" (Indian Rupee), and over 30 others.
  • formatStyle: Determines the output style. Available values are "standard" (e.g., "one hundred twenty-three") and "check" (e.g., "one hundred twenty-three and 00/100"), and "formal" for legal documents.

Use these values to ensure accurate conversions and avoid errors. Example: ?value=123.45&languageCode=en&dialect=US&currencyCode=USD&formatStyle=standard.

Parameters

Parameter Type Required Available Values
value Number Yes Any numerical value (e.g., 123.45)
languageCode String Yes "en", "es", "fr", "de", "it", "pt", "nl", "ru", "ar", "zh", "ja", "ko", "hi", etc. (35+ total)
dialect String Yes Depends on languageCode, e.g., "US", "UK", "AU" for "en"; "ES", "MX" for "es" 
currencyCode String No "USD", "EUR", "GBP", "JPY", "CAD", "AUD", "CHF", "CNY", "INR", etc. (40+ total)
formatStyle String No "standard", "check", and "formal"
debug Boolean No true, false


                                                                            
GET https://zylalabs.com/api/6348/number+to+text+pro+api/9287/getnumbertotext
                                                                            
                                                                        

GetNumberToText - Endpoint Features

Object Description
languageCode [Optional]
currencyCode [Optional]
dialect [Optional]
formatStyle [Optional]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            Twelve million three hundred forty-five thousand six hundred seventy-eight dollars and ninety  cents
                                                                                                                                                                                                                    
                                                                                                    

GetNumberToText - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/6348/number+to+text+pro+api/9287/getnumbertotext' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Number to Text Pro API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

🚀 Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

Number to Text Pro API FAQs

The endpoint returns a JSON object containing a success status, the textual representation of the number, and resolved options such as locale, currency, and format style. For example, it might return "one hundred twenty-three dollars and forty-five cents" for the input number 123.45.

Users can specify parameters such as the numerical value to convert, the desired language and dialect (e.g., "en-US"), optional currency (e.g., "USD"), and formatting style (e.g., "standard" or "formal") to customize the output.

The response data is structured as a JSON object with three main fields: "success" (boolean), "result" (string), and "resolvedOptions" (object). The "resolvedOptions" field includes details like locale, currency, and format style used for the conversion.

Common use cases include generating text for financial documents, legal contracts, invoices, and international communications. It is particularly useful for applications requiring accurate monetary representations in various languages.

Users can extract the "result" field to display the number in text format, while the "resolvedOptions" can help ensure consistency in language and currency across different applications, enhancing user experience and clarity.

Accepted language values include ISO language codes like "en" for English, "es" for Spanish, etc. Currency values should follow ISO 4217 standards, such as "USD" for US dollars or "EUR" for euros, allowing for accurate monetary conversions.

The API relies on established linguistic rules and currency formats to ensure accurate conversions. Regular updates and quality checks are implemented to maintain the integrity of the data across different languages and dialects.

The output typically follows a consistent pattern where numbers are converted into words, formatted according to the specified style. For example, whole numbers are expressed without decimals, while currency values include both whole and fractional parts, ensuring clarity in financial contexts.

General FAQs

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, refer to the ‘X-Zyla-API-Calls-Monthly-Remaining’ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

To see the maximum number of API requests your plan allows, check the ‘X-Zyla-RateLimit-Limit’ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.

The ‘X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.

Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.


Related APIs