About the API:
Be able to recognize any spelling and grammar errors in your application. Receive a JSON object with all the recognized errors, grammar suggestions, and more.
The API will receive the text to check and it will retrieve the errors that it recognizes and potential corrections, all in one JSON object.
Besides the number of API calls per month, there are no other limitations.
{"software":{"name":"GrammarBot","version":"4.3.1","apiVersion":1,"premium":true,"premiumHint":"Thanks for supporting GrammarBot!","status":""},"warnings":{"incompleteResults":false},"language":{"name":"English (US)","code":"en-US","detectedLanguage":{"name":"English (US)","code":"en-US"}},"matches":[{"message":"Is this the personal pronoun 'I'? It is spelled uppercase.","shortMessage":"","replacements":[{"value":"I"}],"offset":0,"length":1,"context":{"text":"i are Alexander.","offset":0,"length":1},"sentence":"i are Alexander.","type":{"typeName":"Other"},"rule":{"id":"I_LOWERCASE","subId":"1","description":"i vs. I","issueType":"misspelling","category":{"id":"TYPOS","name":"Possible Typo"}}},{"message":"Did you mean \"am\" or \"ate\"?","shortMessage":"Possible agreement error","replacements":[{"value":"am"},{"value":"ate"}],"offset":2,"length":3,"context":{"text":"i are Alexander.","offset":2,"length":3},"sentence":"i are Alexander.","type":{"typeName":"Other"},"rule":{"id":"PERS_PRONOUN_AGREEMENT_SENT_START","subId":"2","description":"Agreement: 'I is / you is / ... ' (at sentence start only)","issueType":"grammar","category":{"id":"GRAMMAR","name":"Grammar"}}}]}
curl --location --request POST 'https://zylalabs.com/api/148/spell+and+grammar+checker+api/185/check?text=i are Alexander.&language=en-US' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Check endpoint returns a JSON object containing details about spelling and grammar errors found in the submitted text. This includes error messages, suggested corrections, and contextual information about each error.
Key fields in the response include "matches" (which lists detected errors), "warnings" (for incomplete results), and "language" (indicating the detected language). Each match contains details like the error message, suggested replacements, and context.
The response data is structured as a JSON object with nested fields. The main sections include "software" (API info), "warnings," "language," and "matches," where each match details specific errors and suggestions.
The Check endpoint provides information on spelling and grammar errors, including the type of error, suggested corrections, and contextual details about the text surrounding the error.
The Check endpoint primarily accepts the "text" parameter, which is the input string to be analyzed for errors. Users can customize their requests by varying the text content submitted.
Users can utilize the returned data by reviewing the "matches" array for specific errors and suggested corrections. Each match provides context, allowing users to understand and correct their mistakes effectively.
Data accuracy is maintained through continuous updates and improvements to the underlying algorithms that detect spelling and grammar errors. The API leverages advanced linguistic models to ensure high-quality suggestions.
Typical use cases include enhancing user input validation in applications, proofreading blog articles before publication, and providing real-time feedback to users on spelling and grammar as they type.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
138ms
Service Level:
100%
Response Time:
2,071ms
Service Level:
100%
Response Time:
11,322ms
Service Level:
100%
Response Time:
2,809ms
Service Level:
100%
Response Time:
778ms
Service Level:
100%
Response Time:
2,316ms
Service Level:
100%
Response Time:
687ms
Service Level:
100%
Response Time:
417ms
Service Level:
100%
Response Time:
814ms
Service Level:
100%
Response Time:
279ms