Grammar Check API
Overview
To use Grammar Check, 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/grammarcheckExample
How to call the Grammar Check API in different programming languages.
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"
}'const response = await fetch('https://api.apiverve.com/v1/grammarcheck', {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
},
body: JSON.stringify({
"text": "The the pig snorted when I saw it on the barn gate. I was a little mad becuase it woke up my pupppppy"
})
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
payload = {
"text": "The the pig snorted when I saw it on the barn gate. I was a little mad becuase it woke up my pupppppy"
}
response = requests.post('https://api.apiverve.com/v1/grammarcheck', 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": "The the pig snorted when I saw it on the barn gate. I was a little mad becuase it woke up my pupppppy"
}
jsonPayload, _ := json.Marshal(payload)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/grammarcheck", 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": {
"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"
]
}
]
}
}Authentication
The Grammar Check API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Grammar Check API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Grammar Check API:
Check Grammar and Spelling
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
text | string | required | The text you want to check for grammatical and spelling errors | - |
Response
The Grammar Check 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>
<modified>true</modified>
<corrected>The pig snorted when I saw it on the barn gate. I was a little mad because it woke up my puppy</corrected>
<errorCount>3</errorCount>
<corrections>
<correction>
<rule>repeated_word</rule>
<message>Did you mean to repeat the word "The"?</message>
<position>
<start>0</start>
<end>7</end>
</position>
<suggestions>
<suggestion>The</suggestion>
</suggestions>
</correction>
<correction>
<rule>spelling</rule>
<message>Did you mean "because"?</message>
<position>
<start>67</start>
<end>74</end>
</position>
<suggestions>
<suggestion>because</suggestion>
</suggestions>
</correction>
<correction>
<rule>spelling</rule>
<message>Did you mean "puppy"?</message>
<position>
<start>92</start>
<end>101</end>
</position>
<suggestions>
<suggestion>puppy</suggestion>
</suggestions>
</correction>
</corrections>
</data>
</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
| key | value |
|---|---|
| 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 Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
modified | boolean | Indicates whether any grammar or spelling errors were found | |
corrected | string | The text with grammar and spelling corrections applied | |
errorCount | number | Total number of errors found in the text | |
| [ ] Array items: | array[3] | Array of corrections with details about each error | |
â”” rule | string | The grammar rule that was violated | |
â”” message | string | Description of the error | |
â”” position | object | Start and end position of the error in the text | |
â”” start | number | - | |
â”” end | number | - | |
â”” suggestions | array | Suggested corrections for the error |
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 Grammar Check through GraphQL to combine it with other API calls in a single request. Query only the grammar check 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/graphqlquery {
grammarcheck(
input: {
text: "The the pig snorted when I saw it on the barn gate. I was a little mad becuase it woke up my pupppppy"
}
) {
modified
corrected
errorCount
corrections
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Grammar Check 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
Grammar Check 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 Grammar Check 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 Grammar Check
Official Grammar Check packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Grammar Check works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Grammar Check?
How many credits does Grammar Check cost?
Each successful Grammar Check API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful grammar check lookups.
Can I use Grammar Check in production?
The free plan is for testing and development only. For production use of Grammar Check, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Grammar Check from a browser?
What happens if I exceed my Grammar Check credit limit?
When you reach your monthly credit limit, Grammar Check API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








