Overview
A spell check API you can call to check spelling and correct text: send English text and get back whether it passes, how many distinct misspellings were found, and suggested corrections for each misspelled word. Turn on autocorrect to get correctedText, the text with each misspelling replaced by its first suggestion. Paid plans add total and per-word occurrence counts, and offsets to get the start and end position of every occurrence for highlighting in an editor. Spell Checker works by checking each word of the text against an English dictionary and suggesting likely replacements for the ones it does not recognise.
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!",
"autocorrect": true,
"offsets": true
}'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!",
"autocorrect": true,
"offsets": true
}),
});
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!",
"autocorrect": True,
"offsets": True
},
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!",
"autocorrect": true,
"offsets": true
}`)
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 |
autocorrectOptional | boolean | Include correctedText, the submitted text with each misspelling replaced by its first suggestion |
offsetsOptionalPremium | boolean | Include the start and end character position of every occurrence of each misspelled word |
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,
"totalOccurrences": 2,
"corrections": [
{
"word": "neeed",
"suggestions": [
"needed",
"need",
"needy",
"Neel",
"needs"
],
"occurrences": 1,
"offsets": [
{
"start": 2,
"end": 7
}
]
},
{
"word": "telephine",
"suggestions": [
"telephone",
"telephoned",
"telephoner",
"telephones",
"telephony"
],
"occurrences": 1,
"offsets": [
{
"start": 29,
"end": 38
}
]
}
],
"correctedText": "I needed to call my friend on telephone today!"
}
}
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) |
totalOccurrencesPremium | number | 2 | Total number of misspelled words in the text, counting every repeat |
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 |
occurrencesPremium | number | 1 | How many times the misspelled word appears in the text |
offsetsPremium | array[1] | Position of each occurrence of the misspelled word as start (inclusive) and end (exclusive) character offsets into the submitted text, in UTF-16 code units like JavaScript string indexes (only with offsets=true) | |
startPremium | number | 2 | Character offset where the occurrence begins |
endPremium | number | 7 | Character offset just after the occurrence ends |
correctedText | string | "I needed to call my friend on telephone today!" | The submitted text with each misspelling replaced by its first suggestion, capitalized or upper-cased where the original word was; words with no suggestion are left as written (only with autocorrect=true) |
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: