Text Utilities API - Word Count Slug Hash Base64

API ID 14219

Word and sentence count, reading time, readability and top words; URL slugs; SHA hashes; Base64 encode and decode. All in one text toolkit.

346 ms avg response

API Documentation

Endpoints

Request
Text statistics. Handy text tools in one API: word/sentence count, reading time, Flesch readability and top words; URL slugs; SHA-1/256/384/512 hashes; Base64 encode/decode. GET with 'text' or POST the text.
Endpoint ID: 35292
POST https://zylalabs.com/api/14219/text+utilities+api+-+word+count+slug+hash+base64/35292/text+statistics
INPUT PARAMETERS

Text statistics — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "characters": 21,
    "charactersNoSpaces": 18,
    "words": 4,
    "sentences": 1,
    "paragraphs": 1,
    "readingTimeMinutes": 0.02,
    "speakingTimeMinutes": 0.03,
    "fleschReadingEase": 75.9,
    "topWords": [
        {
            "word": "paste",
            "count": 1
        },
        {
            "word": "your",
            "count": 1
        },
        {
            "word": "text",
            "count": 1
        },
        {
            "word": "here",
            "count": 1
        }
    ]
}
Text statistics — CODE SNIPPETS

curl --location --request POST 'https://zylalabs.com/api/14219/text+utilities+api+-+word+count+slug+hash+base64/35292/text+statistics' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw 'Paste your text here.'

    
Request
Make URL slug. Handy text tools in one API: word/sentence count, reading time, Flesch readability and top words; URL slugs; SHA-1/256/384/512 hashes; Base64 encode/decode. GET with 'text' or POST the text.
Endpoint ID: 35293
GET https://zylalabs.com/api/14219/text+utilities+api+-+word+count+slug+hash+base64/35293/make+url+slug
INPUT PARAMETERS

Make URL slug — Endpoint Features

Object Description
text Required Text (optional)
separator Optional Separator (optional)

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

text
separator
API EXAMPLE RESPONSE
JSON
{
    "text": "Hello World! Ça va?",
    "slug": "hello-world-ca-va"
}
Make URL slug — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14219/text+utilities+api+-+word+count+slug+hash+base64/35293/make+url+slug?text=Hello World! Ça va?&separator=-' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Hash text. Handy text tools in one API: word/sentence count, reading time, Flesch readability and top words; URL slugs; SHA-1/256/384/512 hashes; Base64 encode/decode. GET with 'text' or POST the text.
Endpoint ID: 35294
GET https://zylalabs.com/api/14219/text+utilities+api+-+word+count+slug+hash+base64/35294/hash+text
INPUT PARAMETERS

Hash text — Endpoint Features

Object Description
text Required Text (optional)
algorithm Optional sha1, sha256, sha384, sha512

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

text
algorithm
API EXAMPLE RESPONSE
JSON
{
    "algorithm": "SHA-256",
    "hex": "2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824",
    "base64": "LPJNul+wow4m6DsqxbninhsWHlwfp0JecwQzYpOLmCQ="
}
Hash text — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14219/text+utilities+api+-+word+count+slug+hash+base64/35294/hash+text?text=hello&algorithm=sha256' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Base64. Handy text tools in one API: word/sentence count, reading time, Flesch readability and top words; URL slugs; SHA-1/256/384/512 hashes; Base64 encode/decode. GET with 'text' or POST the text.
Endpoint ID: 35295
GET https://zylalabs.com/api/14219/text+utilities+api+-+word+count+slug+hash+base64/35295/base64
INPUT PARAMETERS

Base64 — Endpoint Features

Object Description
text Required Text (optional)
mode Optional encode or decode

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

text
mode
API EXAMPLE RESPONSE
JSON
{
    "result": "aGVsbG8="
}
Base64 — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14219/text+utilities+api+-+word+count+slug+hash+base64/35295/base64?text=hello&mode=encode' --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 Text Utilities API - Word Count Slug Hash Base64 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.

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

Starts at
$10,000/Year


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

Overview

Word and sentence count, reading time, readability and top words; URL slugs; SHA hashes; Base64 encode and decode. All in one text toolkit.

Text Utilities API - Word Count Slug Hash Base64 FAQs

Each endpoint returns structured JSON data. The Text Statistics endpoint provides metrics like word count, reading time, and readability scores. The Make URL Slug endpoint returns the original text and its corresponding URL-friendly slug. The Hash Text endpoint returns the hash algorithm used, along with the hex and Base64 representations. The Base64 endpoint returns the Base64 encoded result of the input text.

Key fields vary by endpoint. For Text Statistics, fields include "characters," "words," "sentences," and "topWords." The Make URL Slug endpoint returns "text" and "slug." The Hash Text endpoint includes "algorithm," "hex," and "base64." The Base64 endpoint returns "result," which contains the encoded string.

Users can send text data via POST requests or include it as a query parameter in GET requests. The text parameter is essential for all endpoints, allowing users to customize their requests based on the text they want to analyze or transform.

The response data is organized in a JSON format, with each endpoint returning a specific structure. For example, the Text Statistics endpoint returns a summary of text metrics in key-value pairs, while the Hash Text endpoint provides details about the hashing process in a structured format.

Typical use cases include analyzing text for readability, generating URL slugs for SEO, creating secure hashes for data integrity, and encoding/decoding text for data transmission. These functionalities are useful for developers, content creators, and data analysts.

Users can leverage the returned data for various applications. For instance, they can use word counts to gauge text length, employ readability scores to adjust content for target audiences, or generate URL slugs for web pages. The structured format allows easy integration into applications or further processing.

Data accuracy is maintained through consistent algorithms for text analysis and hashing. The API uses established methods for calculating metrics like reading time and readability scores, ensuring reliable outputs. Regular updates and testing help maintain the quality of the API's functionalities.

Users can expect consistent data patterns across endpoints. For example, the Text Statistics endpoint will always return metrics in a similar structure, while the Hash Text endpoint will consistently provide the algorithm type alongside its hash outputs. This predictability aids in seamless integration and data handling.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.

You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.

Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

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.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

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 subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

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.
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]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs