Public APIs
Proofread and Grammar Check API favicon

Proofread and Grammar Check API

Text Analysis

The Proofreading and Grammar Check API ensures the provided text is grammatically correct and polished by automatically proofreading and checking for errors.

Proofread and Grammar Check API's website screenshot

About Proofread and Grammar Check API

Proofread and Grammar Check API is an asynchronous service that checks submitted text for grammar and spelling errors and returns a corrected version. A client submits plain text content to a POST endpoint and receives a job_id and a status_url; the corrected text is then retrieved by polling a GET status endpoint until the job reaches a terminal state. The status response reports one of four states — queued, running, success, or failed — and, once successful, includes the proofread and grammar-corrected text in a result field.

It is intended for content pipelines that need automated language cleanup without blocking the request that submits the text, such as cleaning user-generated content, drafts, support replies, or CMS copy before publishing. The API is published by SharpAPI and listed on ApyHub, at version 1.0.0 with two endpoints (submit and status check). Clients are instructed to poll the status endpoint at most once per second, since faster polling counts against the rate limit without completing the job sooner.

Key features

  • Asynchronous proofreading and grammar-check job submission via POST
  • Poll job status endpoint returns queued, running, success, or failed states
  • Returns corrected text in the result field once the job succeeds
  • Async design avoids blocking the request that submitted the text
  • Rate-limited polling with documented error codes for bad requests, auth, and rate limits

Frequently asked questions

How does this API return results?

You submit text to a POST endpoint which returns a job_id and status_url, then poll the GET status endpoint until the job reaches a success or failed state. The corrected text is available in attributes.result once the job succeeds.

What authentication does it use?

Requests are authenticated with an apy-token header containing an API key.

How often can I poll the job status endpoint?

The documentation recommends polling at most once per second, since faster polling counts against your rate limit without finishing the job sooner.

What errors can the API return?

It can return 400 for a missing or malformed body, 401 for a missing or unauthorized API key, 429 for rate limiting, and 503 when the backend is temporarily unavailable.

Who publishes this API and what is it for?

It is published by SharpAPI and is designed to clean up user-generated content, drafts, support replies, or CMS copy before publishing.

Advertise here

Featured products

  • SerpApi - Search API favicon
  • Screenshot Scout favicon
  • TalorData favicon
  • CoreClaw favicon

Show your product to thousands of developers

· 100k monthly pageviews
· 7k newsletter subscribers

Advertise your product