Paraphrasing API

This documentation is intended to provide you with all of the information you need to work with our service for paraphrasing api.

Paraphrasing API Documentation

This API was created primarily to assist others in using our paraphrasing tool to easily rephrase words, sentences, and paragraphs. Using our API will change the vocabulary and structures, resulting in completely unique and error-free content generated by our powerful AI tool with no training required.

Just Getting Started?

Get can get authorization code after login to our platform. You can also generate or manage authorization codes.

Available languages

Our Paraphrasing API available in 10+ languages: en id da de es fr it pl pt ro sv cs ru th ko

How to use:


To authenticate requests, the API authentication token is used. After logging in, you can view and manage your API Tokens in the Accounts page.

Your API keys have many privileges, so make sure to keep them safe! Do not share your secret API keys in public places like GitHub, client-side code, and so on.

All API requests must include a custom HTTP header called "authorization token." Each programming language's implementation is unique. Further below you can have Here are some examples.

HTTPS is required for all API requests. Calls made over plain HTTP will be rejected. API requests that do not include authentication will also fail.



Paraphrases the given text, makes it an original content.


  • authorization: Bearer {Your API Token} (required)


  • paragraph: String (required)
  • lang: String (required)

Example Call

Below is example api call with CURL. You can follow the example to use out state of the art paraphrasing api endpoint. In this example a post HTTP call is initiate with required params and header with authenticate token.

curl --request POST \
"" \
--header "Authorization: Bearer {YOUR_AUTH_KEY}" \
--header "Content-Type: application/json" \
--header "Accept: application/json
--data-raw '{"paragraph":"{YOUR_TEXT}","lang":"en"}'


Below is a sample response from the endpoint

Call real data:
curl --request POST \
"" \
--header "Authorization: Bearer {YOUR_AUTH_KEY}" \
--header "Content-Type: application/json" \
--header "Accept: application/json
--data-raw '{"paragraph":"Leverage any of its four paraphrasing modes to rewrite the content as required. It enables you to rewrite the content using the standard, fluency, creative, or smarter paraphrasing modes, each of which resonates with a distinct writing style.","lang":"en"}'
Success Result:
{"message": "success",
"content": [
"Leverage any of its 4 paraphrasing modes to rewrite the content material as required. It permits you to rewrite the content material the use of the standard, fluency, creative, or smarter paraphrasing modes, every of which resonates with a wonderful writing style.",
"Use any of the four rephrase modes to rewrite your content as needed. You can rewrite your content using Standard, Fluency, Creative, or Smarter Paraphrasing modes. Each mode reflects a different writing style.",
"Take advantage of one of its four interpretation modes to rewrite content as needed. It allows you to rewrite your content using standard, fluent, creative or clever interpretation modes, each of which creates a distinct writing style.",
"Use one of its four paraphrase modes to rewrite content as needed. It lets you rewrite content using standard, fluent, creative, or smarter paraphrasing modes, each of which resonates with a unique writing style."

Rate Limiting

Each user has his or her own rate limit. When you join the club. Don't worry; you can always ask for more. When you hit a rate limit, the service will stop responding and will return the HTTP 429 response status code (Too many requests) for each request with the JSON string body text.

Error Codes

To indicate the success or failure of an API request, we use standard HTTP response codes. Generally speaking: Codes in the 4xx range indicate a client-side error, which means that the given information did not work (example: parameter missing, expired or missed authorization code). Codes in the 5xx range indicate a server error (which should not occur at all). If the response code is less than 200, the operation failed.

Status Code Explanation
400 - Bad Request The request was unacceptable, often due to missing a required parameter.
401 - Unauthorized No valid API token provided.
404 - Not Found The requested endpoint doesn't exist.
429 - Too many requests request limit exceeded. See section Rate Limiting for more info.
5xx - Server Error We have failed to process your request. You can contact us to let us know.

Response Codes

Success is indicated by codes in the 2xx range. If the response code is not 200, it means the operation failed in some way and you should take appropriate action.

Status Code Explanation
200 - Success Request In return you will get a properly formatted json response.