1st Generation Grammar Check

Getting Started with the GrammarBot API

This page contains information regarding the original GrammarBot API, which will continue to be supported along with the newer GrammarBot Neural service.

The GrammarBot API has been integrated into RapidAPI for the following features:

  • Free package for tinkerers and makers
  • Client code in 10+ programming languages
  • Browser-based testing of requests and results
  • API analytics dashboard

Step 1: Get an API Key from RapidAPI

Use this link to get your API key from RapidAPI (external website). NOTE: for high volume and/or privacy sensitive applications, we allow directly connecting to our servers (i.e., bypassing RapidAPI). Contact us for more information.

Step 2: Submit Text & Receive Grammar Corrections

Using the GrammarBot API is as easy as making a request and receiving suggested spelling and grammar corrections in JSON format. Just add your RapidAPI key in the code below:

/usr/bin/curl -X POST \
      -H "X-RapidAPI-Host: grammarbot.p.rapidapi.com" \  
      -H "X-RapidAPI-Key: **your-rapidapi-key-here**" \  
      -d "language=en-US" \
      -d "text=I can't remember how to go their" \

The Rapid API page for Grammar Bot includes code examples to make a request in more than 10 programming languages. There are also pre-built clients listed below:

Rust - https://github.com/vityafx/grammarbot-io
Send us your own!

NOTE: Browser-based “AJAX” requests will not work due to CORS restrictions. To use in a browser, create a server-side script that acts as a proxy.


Take your learning a step further with these tutorials to help you get up and running quickly:

Request Limits

Grammar Bot offers the most generous free limits on grammar and spelling check, but it’s not unlimited. With an API key, you can receive 500 requests/mo at no cost. Premium options are available for higher volumes.

Document Length Limits

Text longer than 10,000 characters must be split into separate requests. Contact us if your application requires more than this.

NOTE: the information below pertains to the older version of our API that is no longer supported.