Docs/APIs/Grammar Check

Grammar Check

Check grammar and spelling

OperationalCredits 20 per callp50 450msText ProcessingStar

Overview

Pass any raw string in the request body to scan it for grammatical issues and misspelled words. The response states whether modifications were needed, counts the total issues found, and provides the fully revised text. Subscribers on paid plans also receive character offsets, violated rules, and specific replacement suggestions for each error.

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.

POSThttps://api.apiverve.com/v1/grammarcheck
curl -X POST https://api.apiverve.com/v1/grammarcheck \
  -H "x-api-key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "text": "The the pig snorted when I saw it on the barn gate. I was a little mad becuase it woke up my pupppppy"
}'

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.

401 is the only auth verdict

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.

ParameterTypeDescription
textRequiredstringThe text you want to check for grammatical and spelling errors
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.

Sample response
{
  "status": "ok",
  "error": null,
  "data": {
    "modified": true,
    "corrected": "The pig snorted when I saw it on the barn gate. I was a little mad because it woke up my puppy",
    "errorCount": 3,
    "corrections": [
      {
        "rule": "repeated_word",
        "message": "Did you mean to repeat the word \"The\"?",
        "position": {
          "start": 0,
          "end": 7
        },
        "suggestions": [
          "The"
        ]
      },
      {
        "rule": "spelling",
        "message": "Did you mean \"because\"?",
        "position": {
          "start": 67,
          "end": 74
        },
        "suggestions": [
          "because"
        ]
      },
      {
        "rule": "spelling",
        "message": "Did you mean \"puppy\"?",
        "position": {
          "start": 92,
          "end": 101
        },
        "suggestions": [
          "puppy"
        ]
      }
    ]
  }
}

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.

FieldTypeExampleDescription
modifiedbooleantrueIndicates whether any grammar or spelling errors were found
correctedstring"The pig snorted when I saw it on the barn gate. I was a little mad because it woke up my puppy"The text with grammar and spelling corrections applied
errorCountnumber3Total number of errors found in the text
correctionsPremiumarray[3]Array of corrections with details about each error
rulePremiumstring"repeated_word"The grammar rule that was violated
messagePremiumstring"Did you mean to repeat the word "The"?"Description of the error
positionPremiumobject{...}Start and end position of the error in the text
startPremiumnumber0Character offset where the flagged text begins
endPremiumnumber7Character offset where the flagged text ends
suggestionsPremiumarray[The]Suggested corrections for the error

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.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Use cases

Content Management Proofing
Flag grammar mistakes in submitted blog drafts and substitute corrected sentences before publishing articles to readers.
Customer Support Messaging
When agents write replies in ticketing desks, the system uses the error count to warn them of uncorrected typos.
Resume Intake Screening
Job portals scan cover letters during applicant uploads, noting whether the text was modified to preserve clean candidate profiles.
Student Essay Feedback
Learning management platforms pass student submissions to display the number of errors and return properly formatted text.

Other ways to use Grammar Check

Set up Grammar Check on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKitReference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →

More in Text Processing:

Was this page helpful?