Website ReadabilityWebsite Readability API

OnlineCredit Usage:5 per callLive Data
avg: 1976ms|p50: 1798ms|p75: 2095ms|p90: 2450ms|p99: 3162ms

Overview

To use Website Readability, you need an API key. You can get one by creating a free account and visiting your dashboard.

POST Endpoint

URL
https://api.apiverve.com/v1/websitereadability

Example

How to call the Website Readability API in different programming languages.

cURL Request
curl -X POST \
  "https://api.apiverve.com/v1/websitereadability" \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "url": "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts"
}'
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/websitereadability', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "url": "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts"
})
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

payload = {
    "url": "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts"
}

response = requests.post('https://api.apiverve.com/v1/websitereadability', headers=headers, json=payload)

data = response.json()
print(data)
Go (net/http)
package main

import (
    "fmt"
    "io"
    "net/http"
    "bytes"
    "encoding/json"
)

func main() {
    payload := map[string]interface{}{
        "url": "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts"
    }

    jsonPayload, _ := json.Marshal(payload)
    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/websitereadability", bytes.NewBuffer(jsonPayload))

    req.Header.Set("X-API-Key", "your_api_key_here")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}
Example Response
{
  "status": "ok",
  "error": null,
  "data": {
    "fleschReadingEase": 24.34,
    "fleschReadingEaseText": "Very Confusing",
    "fleschKincaidGrade": 19.3,
    "gunningFog": 19.62,
    "colemanLiauIndex": 13.12,
    "smogIndex": 14.37,
    "automatedReadabilityIndex": 22.6,
    "daleChallReadabilityScore": 17,
    "daleChallReadabilityScoreText": "average 13th to 15th-grade (college) student",
    "url": "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts"
  }
}

Authentication

The Website Readability API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the Website Readability API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Website Readability API:

Analyze Website Readability

ParameterTypeRequiredDescriptionDefaultExample
urlstringrequired
The URL of the web page to analyze
Format: url (e.g., https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts)
-https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts

Response

The Website Readability API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.

Other Response Formats

XML Response
200 OK
<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <fleschReadingEase>24.34</fleschReadingEase>
    <fleschReadingEaseText>Very Confusing</fleschReadingEaseText>
    <fleschKincaidGrade>19.3</fleschKincaidGrade>
    <gunningFog>19.62</gunningFog>
    <colemanLiauIndex>13.12</colemanLiauIndex>
    <smogIndex>14.37</smogIndex>
    <automatedReadabilityIndex>22.6</automatedReadabilityIndex>
    <daleChallReadabilityScore>17</daleChallReadabilityScore>
    <daleChallReadabilityScoreText>average 13th to 15th-grade (college) student</daleChallReadabilityScoreText>
    <url>https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts</url>
  </data>
</response>
YAML Response
200 OK
status: ok
error: null
data:
  fleschReadingEase: 24.34
  fleschReadingEaseText: Very Confusing
  fleschKincaidGrade: 19.3
  gunningFog: 19.62
  colemanLiauIndex: 13.12
  smogIndex: 14.37
  automatedReadabilityIndex: 22.6
  daleChallReadabilityScore: 17
  daleChallReadabilityScoreText: average 13th to 15th-grade (college) student
  url: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts
CSV Response
200 OK
keyvalue
fleschReadingEase24.34
fleschReadingEaseTextVery Confusing
fleschKincaidGrade19.3
gunningFog19.62
colemanLiauIndex13.12
smogIndex14.37
automatedReadabilityIndex22.6
daleChallReadabilityScore17
daleChallReadabilityScoreTextaverage 13th to 15th-grade (college) student
urlhttps://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains the API response data if successful, otherwise null{...}

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

Response fields marked with Premium are available exclusively on paid plans.View pricing
FieldTypeSample ValueDescription
fleschReadingEasenumber24.34
Flesch Reading Ease score (0-100, higher is easier)
fleschReadingEaseTextstring"Very Confusing"
Descriptive text interpretation of Flesch Reading Ease
fleschKincaidGradenumber19.3
Flesch-Kincaid Grade Level (US school grade equivalency)
gunningFogPremiumnumber19.62
Gunning Fog Index (years of education needed to understand)
colemanLiauIndexPremiumnumber13.12
Coleman-Liau Index (US grade level based on character count)
smogIndexPremiumnumber14.37
SMOG Index (years of education to understand text)
automatedReadabilityIndexPremiumnumber22.6
Automated Readability Index (US grade level estimate)
daleChallReadabilityScorePremiumnumber17
Dale-Chall Readability Score (educational level)
daleChallReadabilityScoreTextPremiumstring"average 13th to 15th-grade (college) student"
Descriptive interpretation of Dale-Chall Readability Score
urlstring"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts"
The analyzed URL from the request

Headers

Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →

GraphQL AccessALPHA

Access Website Readability through GraphQL to combine it with other API calls in a single request. Query only the website readability data you need with precise field selection, and orchestrate complex data fetching workflows.

Test Website Readability in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  websitereadability(
    input: {
      url: "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts"
    }
  ) {
    fleschReadingEase
    fleschReadingEaseText
    fleschKincaidGrade
    gunningFog
    colemanLiauIndex
    smogIndex
    automatedReadabilityIndex
    daleChallReadabilityScore
    daleChallReadabilityScoreText
    url
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The Website Readability API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →

Rate Limiting

Website Readability requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →

Error Codes

The Website Readability API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →

SDKs for Website Readability

Official Website Readability packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

No-Code Integrations

Website Readability works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Frequently Asked Questions

How do I get an API key for Website Readability?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for Website Readability and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does Website Readability cost?

Each successful Website Readability API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful website readability lookups.

Can I use Website Readability in production?

The free plan is for testing and development only. For production use of Website Readability, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.

Can I use Website Readability from a browser?
Yes! The Website Readability API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my Website Readability credit limit?

When you reach your monthly credit limit, Website Readability API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?