Gibberish DetectorGibberish Detector API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 463ms|p50: 438ms|p75: 480ms|p90: 530ms|p99: 630ms

Overview

To use Gibberish Detector, 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/gibberishdetector

Example

How to call the Gibberish Detector API in different programming languages.

cURL Request
curl -X POST \
  "https://api.apiverve.com/v1/gibberishdetector" \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "text": "The quick brown fox jumps over the lazy dog"
}'
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/gibberishdetector', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "text": "The quick brown fox jumps over the lazy dog"
})
});

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 = {
    "text": "The quick brown fox jumps over the lazy dog"
}

response = requests.post('https://api.apiverve.com/v1/gibberishdetector', 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{}{
        "text": "The quick brown fox jumps over the lazy dog"
    }

    jsonPayload, _ := json.Marshal(payload)
    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/gibberishdetector", 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": {
    "isGibberish": false,
    "score": 0.12,
    "confidence": 88,
    "confidenceLevel": "high",
    "text": "The quick brown fox jumps over the lazy dog",
    "textLength": 43,
    "wordCount": 9
  }
}

Authentication

The Gibberish Detector 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 Gibberish Detector API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Gibberish Detector API:

Detect Gibberish Text

ParameterTypeRequiredDescriptionDefaultExample
textstringrequired
Text to analyze (max 10,000 characters)
-asdfghjkl qwerty

Response

The Gibberish Detector 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>
    <isGibberish>false</isGibberish>
    <score>0.12</score>
    <confidence>88</confidence>
    <confidenceLevel>high</confidenceLevel>
    <text>The quick brown fox jumps over the lazy dog</text>
    <textLength>43</textLength>
    <wordCount>9</wordCount>
  </data>
</response>
YAML Response
200 OK
status: ok
error: null
data:
  isGibberish: false
  score: 0.12
  confidence: 88
  confidenceLevel: high
  text: The quick brown fox jumps over the lazy dog
  textLength: 43
  wordCount: 9
CSV Response
200 OK
keyvalue
isGibberishfalse
score0.12
confidence88
confidenceLevelhigh
textThe quick brown fox jumps over the lazy dog
textLength43
wordCount9

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:

FieldTypeSample ValueDescription
isGibberishbooleanfalse
Whether the text is detected as gibberish
scorenumber0.12
Gibberish score from 0 to 1 (higher = more gibberish)
confidencenumber88
Detection confidence percentage (0-100)
confidenceLevelstring"high"
Confidence level: high, medium, or low
textstring"The quick brown fox jumps over the lazy dog"
The original text that was analyzed
textLengthnumber43
Character count of the input text
wordCountnumber9
Number of words in the text

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 Gibberish Detector through GraphQL to combine it with other API calls in a single request. Query only the gibberish detector data you need with precise field selection, and orchestrate complex data fetching workflows.

Test Gibberish Detector 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 {
  gibberishdetector(
    input: {
      text: "The quick brown fox jumps over the lazy dog"
    }
  ) {
    isGibberish
    score
    confidence
    confidenceLevel
    text
    textLength
    wordCount
  }
}

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

CORS Support

The Gibberish Detector 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

Gibberish Detector 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 Gibberish Detector 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 Gibberish Detector

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

No-Code Integrations

Gibberish Detector 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 Gibberish Detector?
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 Gibberish Detector and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does Gibberish Detector cost?

Each successful Gibberish Detector 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 gibberish detector lookups.

Can I use Gibberish Detector in production?

The free plan is for testing and development only. For production use of Gibberish Detector, 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 Gibberish Detector from a browser?
Yes! The Gibberish Detector 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 Gibberish Detector credit limit?

When you reach your monthly credit limit, Gibberish Detector 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?