Spell Checker API

Overview

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

POST Endpoint

https://api.apiverve.com/v1/spellchecker

Example

How to call the Spell Checker API in different programming languages.

curl -X POST \
  "https://api.apiverve.com/v1/spellchecker" \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "text": "I neeed to call my friend on telephine today!"
}'

const response = await fetch('https://api.apiverve.com/v1/spellchecker', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "text": "I neeed to call my friend on telephine today!"
})
});

const data = await response.json();
console.log(data);

import requests

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

payload = {
    "text": "I neeed to call my friend on telephine today!"
}

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

data = response.json()
print(data)

package main

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

func main() {
    payload := map[string]interface{}{
        "text": "I neeed to call my friend on telephine today!"
    }

    jsonPayload, _ := json.Marshal(payload)
    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/spellchecker", 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))
}

{
  "status": "ok",
  "error": null,
  "data": {
    "spellPass": false,
    "mispellingsFound": 2,
    "corrections": [
      {
        "word": "neeed",
        "suggestions": [
          "needed",
          "need",
          "needy",
          "Neel",
          "needs"
        ]
      },
      {
        "word": "telephine",
        "suggestions": [
          "telephone",
          "telephoned",
          "telephoner",
          "telephones",
          "telephony"
        ]
      }
    ]
  }
}

Authentication

The Spell Checker API requires authentication via API key. Include your API key in the request header:

X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the Spell Checker API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Spell Checker API:

Response

The Spell Checker 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 version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <spellPass>false</spellPass>
    <mispellingsFound>2</mispellingsFound>
    <corrections>
      <correction>
        <word>neeed</word>
        <suggestions>
          <suggestion>needed</suggestion>
          <suggestion>need</suggestion>
          <suggestion>needy</suggestion>
          <suggestion>Neel</suggestion>
          <suggestion>needs</suggestion>
        </suggestions>
      </correction>
      <correction>
        <word>telephine</word>
        <suggestions>
          <suggestion>telephone</suggestion>
          <suggestion>telephoned</suggestion>
          <suggestion>telephoner</suggestion>
          <suggestion>telephones</suggestion>
          <suggestion>telephony</suggestion>
        </suggestions>
      </correction>
    </corrections>
  </data>
</response>

status: ok
error: null
data:
  spellPass: false
  mispellingsFound: 2
  corrections:
    - word: neeed
      suggestions:
        - needed
        - need
        - needy
        - Neel
        - needs
    - word: telephine
      suggestions:
        - telephone
        - telephoned
        - telephoner
        - telephones
        - telephony

Response Structure

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

Learn more about response formats →

Response Data Fields

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

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

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

POST https://api.apiverve.com/v1/graphql

query {
  spellchecker(
    input: {
      text: "I neeed to call my friend on telephine today!"
    }
  ) {
    spellPass
    mispellingsFound
    corrections
  }
}

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

CORS Support

The Spell Checker 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

Spell Checker 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 Spell Checker 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 Spell Checker

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

JitPack

No-Code Integrations

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

Zapier

Make

Pipedream

n8n

Power Automate

Frequently Asked Questions

People who used this also used...

Based on your interest in Spell Checker, you might also like these APIs:

Rhyming Words

Word Rhymes is a simple tool for getting word rhymes. It returns a list of rhyming words.

1 credit per call

Word Pronunciation

Word Pronunciation is a simple tool for getting the pronunciation of a word. It returns the pronunciation of the word provided.

1 credit per call

Word Opposites

Word Opposites is a simple tool for getting the opposites of a word. It returns a list of opposites for the given word.

10 credits per call