Grammar Check API

About the Grammar Check API

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.

What people use it for

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.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — POST /v1/grammarcheck

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

1
2
3
4

curl -X POST "https://api.apiverve.com/v1/grammarcheck" \
  -H "x-api-key: YOUR_API_KEY" \
  -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"}'

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — POST /v1/grammarcheck

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

{
  "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.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 20 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive Grammar Check form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — Grammar Check API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1