Overview
Spell Checker works by using a dictionary of words to check the spelling of a given text. Using advanced algorithms and the entire English dictionary, it returns the corrected text.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
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 res = 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!"
}),
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.post(
"https://api.apiverve.com/v1/spellchecker",
headers={"x-api-key": "your_api_key_here"},
json={
"text": "I neeed to call my friend on telephine today!"
},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
"strings"
)
func main() {
body := strings.NewReader(`{
"text": "I neeed to call my friend on telephine today!"
}`)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/spellchecker", body)
req.Header.Set("Content-Type", "application/json")
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
textRequired | string | The text to check the spelling of length 0–50000 |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"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 fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
spellPass | boolean | false | Whether the text passed the spell check with no misspellings detected |
mispellingsFound | number | 2 | Count of distinct misspelled words found in the text (a word repeated multiple times is only counted once) |
corrections | array[2] | List of distinct misspelled words found in the text, each with suggested corrections | |
word | string | "neeed" | The misspelled word as it appeared in the text |
suggestions | array | [needed, ...] | Up to five candidate correct spellings for the misspelled word, ordered by the dictionary's relevance ranking |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Rich Text Editors
- Flag typos in user-submitted drafts in real time and display replacement suggestions directly inside the editing interface.
- Customer Support Chat
- Before sending agent replies to customers, scan message drafts to detect misspelled words and prevent communication errors.
- Form Submission Sanitization
- Job boards inspect candidate resumes and cover letters upon upload to tally spelling mistakes before forwarding applications to recruiters.
- Student Essay Assessment
- To automate rubric scoring, learning platforms scan student papers to count uncorrected typos and show teachers the identified errors.
Other ways to use Spell Checker
Set up Spell Checker on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Text Processing: