Introduction

The Rephraser API is a comprehensive solution designed to enhance content creation and management with advanced paraphrasing, summarization, and text optimization capabilities. It empowers developers to seamlessly integrate diverse text-enhancement tools into their applications, catering to a variety of writing styles and requirements.

BASE URL

https://www.rephraser.co/api

All API's End Points

  • - GET – [base_url]/plan/details
  • - GET – [base_url]/usage/details
  • - POST – [base_url]/rephrase
  • - POST – [base_url]/humanize
  • - POST – [base_url]/summarizer
  • - POST – [base_url]/plagiarism-remover
  • - POST – [base_url]/article-rewriter
  • - POST – [base_url]/grammar-checker
Key Features:

Plan Details: Retrieve information about the user's subscribed plan, including:

  • Total and available API credits
  • Renewal date & Amount

Usage Details: The Usage Detail API provides an overview of your credit usage and detailed logs of API requests. It helps track credit consumption, monitor API activities, and analyze usage patterns effectively. This API is ideal for maintaining transparency and optimizing your credit utilization.

Rephrase: Tailor content to specific tones and styles:

  • Creative: Generate imaginative and varied language.
  • Formal: Adjust language for professional or official contexts.
  • Fluent: Ensure readability and natural flow.
  • Academic: Maintain scholarly tone and vocabulary.
  • Blog: Optimize for engaging, conversational language.
  • Humanizer: Transform mechanical or overly complex text into relatable, easy-to-understand language.
  • Summarizer: Condense lengthy documents into brief, comprehensive summaries.
  • Plagiarism Remover: Adapt content to ensure originality and prevent duplication.
  • Article Rewriter: Restructure and refine articles for improved readability, coherence, and uniqueness while maintaining the original meaning.
  • Grammar Checker: Automatically detect and correct grammatical errors, enhancing text quality and accuracy.

Create

Create and submit a task for text humanization.

Name Description
api-key
Authentication API key to access the endpoint.
string (header)

Example Value
{
"input": "string",
"model_type":
"Quick"
}

Code
200
Description
Successfully retrieved task details.
Media Type Control accept header
Example Value
{
"input": "string",
"model_type":
"Quick"
}

Retrieve

Retrieve the results of your submitted text humanization task.

Name
Description
api-key
Authentication API key to access the endpoint.
string (header)
Task-id
Unique identifier for the task to be retrieved.
string (query)

Code
200
Description
Successfully retrieved task details.
Media Type Control accept header
Example Value
{
"err_code": 0,
"err_msg": "Success",
"data": {
"input": "How to Give a Great Gift to Someone\n\n\nChoosing the perfect gift for someone can be a delightful experience when you consider their preferences and interests. Here's a guide on how to give a great gift that will be appreciated and cherished:\n\n\n1. Know the Recipient: Take the time to understand the person you're buying for. Consider their hobbies, interests, and personality. What makes them happy?\n\n\n2. Listen and Observe: Pay attention to any hints or mentions of things they want or need. Sometimes, people drop subtle hints about what they'd like as a gift.\n\n\n3. Consider Practicality: A useful gift can be just as thoughtful as a sentimental one. Think about what would make the recipient's life easier or more enjoyable.",
"input_words": 122,
"task_id": "2c451bac-c5ea-4e77-a21a-23ebc14ba47f",
"words_used": 97,
"output": "How to Give a Great Gift to Someone\n\nChoosing the perfect present for another requires deep reflection on their passions and pursuits. A guide for bestowing a gift certain to be cherished:\n\n1. Fathoming the recipient entails comprehending their diversions, interests, and persona. What lifts their spirit? \n\n2. Heed hints and allusions to objects they covet or necessities they require, whether oblique or overt. Subtle signposts sometimes indicate coveted offerings.\n\n3. Pondering usefulness alongside sentiment, a present easing life or amplifying joy merits equal thought. Consider how your selection may delight through facilitating pleasure or alleviating burden.",
"subtask_status": "completed",
"task_status": true,
"detection_result": "human",
"detection_score": 100,
"mode": "Advanced"
}
}
API Authentication

Every user is assigned a unique API key upon registration. This API key is required for authenticating requests to the Rephraser API. Requests that do not include a valid API key will return a 401 , 403 Forbidden error, preventing access to the API's features.

Your API Key

create_your_key

Header Parameter

['x-api-key: create_your_api_key']
API Error Code

The Rephraser API returns consistent responses to indicate the success or failure of each request. The response will include specific codes and messages to make it easy to understand the request’s status.

Possible Enum Values

Success : success, response, data, message, status=true
Error : error , api_error, exception, error_message, status=false

HTTP Status Code Summary

200

OK

The request was successful.

400

Bad Request

The request was unacceptable, often due to missing a required parameter.

401

Unauthorized

No valid API key provided.

403

Forbidden

Doesn’t have permissions to perform the request.

404

Not Found

The requested resource doesn’t exist.

429

Too Many Requests

Too many requests hit the API too quickly.

500

Server Errors

Something went wrong on Rephraser end.

Plan Details

This endpoint returns details of the user's subscribed plan, including the total and available API credits, along with the renewal date and amount.

Header:

  • Headers: The request must include an API key in the header for authentication.
  • Headers
    • x-api-key: (Required) - The API key used for authentication.

Response:

The API responds with a JSON object containing the subscribed plan, credit & renew details.

Response Parameters:

  • status: (integer) - HTTP status code (200 indicates success).
  • message: (string) - A message confirming the success of the request.
  • plan_detail : (object) - Contains the details of the user's subscribed plan.
    • subscribed_plan_id (string): The unique ID of the subscribed plan.
    • plan_name (string): The name of the subscribed plan (e.g., "yearly").
    • total_api_credit (string): The total number of API credits allocated to the plan.
    • total_api_credit_in_k (string): The total number of API credits in a human-readable format (e.g., "500k").
    • available_api_credit (string): The available number of API credits remaining in the plan.
    • available_api_credit_in_k (string): The available number of API credits in a human-readable format.
    • renew_at (string): The date when the plan will be renewed (format: MM-DD-YYYY).
    • renew_amount (string): The amount to be charged on renewal (e.g., "$350").

Plan Detail URL

- GET - {base_url}/plan/details

HTTP Request Header

['x-api-key: create_your_api_key']

Response

{
  "status": 200,
  "message": "Subscribed plan detail with usage",
  "plan_detail": {
    "subscribed_plan_id": "sub_1QHghE2KSqiTg9wqwanQX1gS",
    "plan_name": "yearly",
    "total_api_credit": "500000",
    "total_api_credit_in_k": "500k",
    "available_api_credit": "492194",
    "available_api_credit_in_k": "492k",
    "renew_at": "11-05-2025",
    "renew_amount": "$350"
  }
}
Usage Details

The Usage Detail API provides detailed insights into the usage of credits, including overall credit consumption and individual API usage logs. This API is useful for monitoring credit consumption and analyzing usage patterns.

Header:

  • Headers: The request must include an API key in the header for authentication.
  • Headers
    • x-api-key: (Required) - The API key used for authentication.

Response:

The API responds with a JSON object containing the total credit details and a breakdown of usage activities.

Response Parameters:

  • status: (integer) - HTTP status code (200 indicates success).
  • message: (string) - A descriptive message indicating the response status.
  • total_credit: (string) - The total number of credits available, formatted with commas for readability.
  • total_used_credit: (string) - The total number of credits used, formatted with commas for readability.
  • usage_detail : (array) - A list of usage logs, where each log contains:
    • ip_address (string): The IP address of the user or source of the API request.
    • browser (string): Information about the browser or client making the request.
    • origin (string): The origin or referring service associated with the API usage.
    • api_mode (string): The specific API mode used (e.g. humanize, grammar_checker).
    • input_txt (string): The input text provided in the API request.
    • output_txt (string): The output text generated by the API.
    • api_credit (string): The number of credits consumed for this request.
    • created_at (string): The timestamp indicating when this API request was made.

Usage Detail URL

- GET - {base_url}/usage/details

HTTP Request Header

['x-api-key: create_your_api_key']

Response

{
  "status": 200,
  "message": "Usage detail with api credits.",
  "total_credit": "500,000",
  "total_used_credit": "8,135",
  "usage_detail": [
    {
      "ip_address": "127.0.0.1",
      "browser": "null",
      "origin": "null",
      "api_mode": "humanize",
      "input_txt": "The Beginning of Ranjha's Journey\n\nRanjha, whose full name was Dheedo Ranjha, was the youngest of four brothers born into a well-to-do family in the village of Takht Hazara, on the banks of the Chenab River. Unlike his elder brothers, who were more inclin",
      "output_txt": "The Beginning of Ranjha's Journey.\n\n Dheedo Ranjha, the youngest of four brothers, was born into a wealthy family in the village of Takht Hazara by the Chenab River. Unlike his older siblings, who preferred agriculture and estate management, Ranjha was",
      "api_credit": "954"
      "created_at": "2024-11-08 06:12:03",
    },
    {
      "ip_address": "127.0.0.1",
      "browser": "null",
      "origin": "null",
      "api_mode": "summarizer",
      "input_txt": "The Beginning of Ranjha's Journey\n\nRanjha, whose full name was Dheedo Ranjha, was the youngest of four brothers born into a well-to-do family in the village of Takht Hazara, on the banks of the Chenab River. Unlike his elder brothers, who were more inclin",
      "output_txt": "The Beginning of Ranjha's Journey.\n\n Dheedo Ranjha, the youngest of four brothers, was born into a wealthy family in the village of Takht Hazara by the Chenab River. Unlike his older siblings, who preferred agriculture and estate management, Ranjha was",
      "api_credit": "954"
      "created_at": "2024-11-08 06:12:03",
    },
  ]
}
Rephrase

This API endpoint allows you to rephrase content in different modes (Creative, Fluence, Formal, Academic, and Blog) based on the input provided. The response will include the rephrased content, word count statistics, and the percentage of change.

Request:

  • Content-Type: multipart/form-data
  • Headers: The request must include an API key in the header for authentication.
  • Body Parameters
    • input_content: (string) - The text to be humanized.
    • lang: (string) - The language code of the input content (e.g: en, es, fr).
    • mode: (string) - The mode in which the content should be rephrased. The available modes are: (creative, fluence, formal, academic, and blog).
Note: freeze_words (string, optional for Blog mode only): A comma-separated list of words that should not be rephrased. This is only used when the mode is set to Blog.

Response:

The response format will remain the same for all modes, with the only difference being the prefix in the response field (e.g., blog_text for Blog mode, creative_text for Creative mode, etc.):

Response Parameters:

  • status: (integer) - HTTP status code (200 indicates success).
  • message: (string) - A message describing the status of the rephrasing operation.
  • [mode]_text: (string) - The rephrased content in HTML format with <span></span> tags. The mode will vary depending on the selected mode (e.g., creative_text, fluent_text, formal_text, academic_text, blog_text).
  • [mode]_plain_text: (string) - The rephrased content in plain text format, without <span></span> tags.
  • percentage: (float) - The percentage similarity between the input and humanized text, reflecting the degree of change.
  • input_word_count: (integer) - The word count of the original input text.
  • output_word_count: (integer) - The word count of the humanized output text.

Humanize URL

- POST - {base_url}/rephrase

HTTP Request Header

['x-api-key: create_your_api_key']

HTTP Request Body

[
  "input_content" => "In today’s fast-paced digital world, it’s crucial for businesses to stay connected with their customers in a personalized way. As technology evolves, so do the expectations of consumers who now seek not only convenience but also meaningful engagement.",
  "freeze_words" => "technological , modern" (This parameter only for 'blog' mode.),
  "lang" => "en",
  "mode" => "blog"
]

Response

{
  "status": 200,
  "message": "Content blog successfully",
  "blog_text": "<span>Today's</span> <span>swiftly</span> <span>evolving</span> <span>tech</span> <span>environment</span> <span>necessitates</span> <span>companies</span> to <span>maintain</span> <span>individualized</span> <span>connections</span> with their <span>clientele.</span> As <span>tech</span> <span>advances,</span> <span>consumer</span> <span>demands</span> <span>shift</span> <span>towards</span> not <span>just</span> <span>ease</span> but also <span>significant</span> <span>involvement.</span>",
  "blog_plain_text": " Today's swiftly evolving tech environment necessitates companies to maintain individualized connections with their clientele. As tech advances, consumer demands shift towards not just ease but also significant involvement.",
  "percentage": 87.9310,
  "input_word_count": 40,
  "output_word_count": 28
}
Humanize

The Humanize API is designed to make text sound more natural and relatable by adjusting the tone and phrasing. This endpoint is especially useful for creating content that connects with audiences on a more personal level. It transforms overly formal or robotic text into language that feels conversational and human-friendly.

Request:

  • Content-Type: multipart/form-data
  • Headers: The request must include an API key in the header for authentication.
  • Body Parameters
    • input_content: (string) - The text to be humanized.
    • lang: (string) - The language code of the input content (e.g., en for English, es for Spanish, fr for French).

Response:

The API responds with a JSON object containing the humanized version of the text, both with and without HTML <span></span> tags, as well as information about the transformation process.

Response Parameters:

  • status: (integer) - HTTP status code (200 indicates success).
  • message: (string) - A message confirming the success of the request.
  • humanized_text: (string) - The humanized text with <span></span> tags around specific words that were modified or emphasized.
  • humanized_plain_text: (string) - The humanized text without any HTML tags.
  • percentage: (float) - The percentage similarity between the input and humanized text, reflecting the degree of change.
  • input_word_count: (integer) - The word count of the original input text.
  • output_word_count: (integer) - The word count of the humanized output text.

Humanize URL

- POST - {base_url}/humanize

HTTP Request Header

['x-api-key: create_your_api_key']

HTTP Request Body

[
  "input_content" => "In today’s fast-paced digital world, it’s crucial for businesses to stay connected with their customers in a personalized way. As technology evolves, so do the expectations of consumers who now seek not only convenience but also meaningful engagement.",
  "lang" => "en"
]

Response

{
  "status": 200,
  "message": "Content humanized successfully",
  "blog_text": "<span>Today's</span> <span>swiftly</span> <span>evolving</span> <span>tech</span> <span>environment</span> <span>necessitates</span> <span>companies</span> to <span>maintain</span> <span>individualized</span> <span>connections</span> with their <span>clientele.</span> As <span>tech</span> <span>advances,</span> <span>consumer</span> <span>demands</span> <span>shift</span> <span>towards</span> not <span>just</span> <span>ease</span> but also <span>significant</span> <span>involvement.</span>",
  "blog_plain_text": " Today's swiftly evolving tech environment necessitates companies to maintain individualized connections with their clientele. As tech advances, consumer demands shift towards not just ease but also significant involvement.",
  "percentage": 87.9310,
  "input_word_count": 40,
  "output_word_count": 28
}
Summarizer

The Summarizer API condenses lengthy content into a shorter, more concise version, highlighting the main points. It is particularly useful for creating summaries of articles, reports, and other types of long-form content, enabling users to quickly grasp key information.

Request:

  • Content-Type: multipart/form-data
  • Headers: The request must include an API key in the header for authentication.
  • Body Parameters
    • input_content: (string) - The text to be summarized.

Response:

The API responds with a JSON object containing the summarized text, bullet points, keywords, and other useful summary details.

Response Parameters:

  • status: (integer) - HTTP status code (200 indicates success).
  • message: (string) - A message confirming the success of the request.
  • summarized_text: (string) - The main summary of the input text, providing a concise overview.
  • bullet_points: (string) - A bulleted list of key points derived from the input content.
  • keywords: (array of strings) - A list of important keywords extracted from the content.
  • best_line: (string) - The most important sentence identified from the input content.
  • input_word_count: (integer) - The word count of the original input text.

Notes:

  • The summarized_text field provides a brief summary of the input content, while the bullet_points field presents key ideas in a list format, making it easy to read.
  • The keywords array highlights the essential terms, giving insights into the main topics of the content.

Summarize URL

- POST - {base_url}/summarize

HTTP Request Header

['x-api-key: create_your_api_key']

HTTP Request Body

[
  "input_content" => "In today’s fast-paced digital world, it’s crucial for businesses to stay connected with their customers in a personalized way. As technology evolves, so do the expectations of consumers who now seek not only convenience but also meaningful engagement.",
]

Response

{
  "status": 200,
  "message": "Content summarized successfully",
  "summarized_text": "In today’s fast-paced digital world, it’s crucial for businesses to stay connected with their customers in a personalized way. As technology evolves, so do the expectations of consumers who now seek not only convenience but also meaningful engagement.",
  "bullet_points": "\n• In today’s fast-paced digital world, it’s crucial for businesses to stay connected with their customers in a personalized way.\n• As technology evolves, so do the expectations of consumers who now seek not only convenience but also meaningful engagement.\n\n",
  "keywords": ["businesses", "expectations", "fast", "meaningful", "paced", "personalized", "seek", "stay", "technology", "today"],
  "best_line": "In today’s fast-paced digital world, it’s crucial for businesses to stay connected with their customers in a personalized way."
  "input_word_count": 40 ,
}
Plagraism Remover

The Plagiarism Remover API helps rephrase content to avoid plagiarism while retaining the original meaning. It is ideal for users looking to create unique versions of text, ensuring that the content is original and free from duplication.

Request:

  • Content-Type: multipart/form-data
  • Headers: The request must include an API key in the header for authentication.
  • Body Parameters
    • input_content: (string) - The text to be avoid plagiarism.

Response:

The API responds with a JSON object containing the rephrased text, free from plagiarism, along with related details.

Response Parameters:

  • status: (integer) - HTTP status code (200 indicates success).
  • message: (string) - A message confirming the success of the request.
  • plagiarism_removed_text: (string) - The rephrased text containing <span></span> tags to highlight the words changed to remove plagiarism.
  • plagiarism_removed_plain_text: (string) - The plain text version of the rephrased content without <span></span> tags.
  • percentage: (float) - The percentage of content that was modified to achieve plagiarism-free text.
  • input_word_count: (integer) - The word count of the original input text.
  • output_word_count: (integer) - The word count of the rephrased output text.

Plagraism Remover URL

- POST - {base_url}/plagiarism-remover

HTTP Request Header

['x-api-key: create_your_api_key']

HTTP Request Body

[
  "input_content" => "In today’s fast-paced digital world, it’s crucial for businesses to stay connected with their customers in a personalized way. As technology evolves, so do the expectations of consumers who now seek not only convenience but also meaningful engagement.",
]

Response

{
  "status": 200,
  "message": "Content plagiarism removed successfully",
  "plagiarism_removed_text": "In <span>the</span> <span>modern</span> <span>era</span> <span>of</span> <span>rapid</span> <span>technological</span> <span>advancements,</span> <span>it</span> <span>is</span> <span>of</span> <span>utmost</span> <span>importance</span> for <span>companies</span> to <span>maintain</span> <span>a</span> <span>strong</span> <span>connection</span> with their customers <span>through</span> personalized <span>communication.</span> As technology <span>advances,</span> <span>consumers'</span> expectations <span>also</span> <span>evolve,</span> <span>demanding</span> not only convenience but also <span>a</span> <span>sense</span> <span>of</span> <span>connection</span> <span>and</span> engagement.",
  "plagiarism_removed_plain_text": "In the modern era of rapid technological advancements, it is of utmost importance for companies to maintain a strong connection with their customers through personalized communication. As technology advances, consumers' expectations also evolve, demanding not only convenience but also a sense of connection and engagement.",
  "percentage": 67.79661016949152,
  "input_word_count": 40,
  "output_word_count": 45
}
Article Rewriter

The Article Rewriter API enables users to transform existing text into a fresh, unique version while preserving the original meaning. It is ideal for content creators, marketers, and bloggers looking to generate high-quality, plagiarism-free rewritten articles with ease.

Request:

  • Content-Type: multipart/form-data
  • Headers: The request must include an API key in the header for authentication.
  • Body Parameters
    • input_content: (string) - The text to be rewritten.

Response:

The API responds with a JSON object containing the rewritten content and relevant details.

Response Parameters:

  • status: (integer) - HTTP status code (200 indicates success).
  • message: (string) - A message confirming the success of the request.
  • rewritten_text : (string) - The rewritten version of the input text with <span></span> tags highlighting the changes.
  • rewritten_plain_text : (string) - The rewritten text without any <span></span> tags.
  • percentage: (float) - The percentage of words or phrases modified during rewriting.
  • input_word_count: (integer) - The word count of the original input text.
  • output_word_count: (integer) - The word count of the rewritten output text.

Article Rewriter URL

- POST - {base_url}/article-rewriter

HTTP Request Header

['x-api-key: create_your_api_key']

HTTP Request Body

[
  "input_content" => "In today’s fast-paced digital world, it’s crucial for businesses to stay connected with their customers in a personalized way. As technology evolves, so do the expectations of consumers who now seek not only convenience but also meaningful engagement.",
]

Response

{
  "status": 200,
  "message": "Content rewrite successfully",
  "rewritten_text": "In <span>the</span> <span>modern</span> <span>era</span> <span>of</span> <span>rapid</span> <span>technological</span> <span>advancements,</span> <span>it</span> <span>is</span> <span>of</span> <span>utmost</span> <span>importance</span> for <span>companies</span> to <span>maintain</span> <span>a</span> <span>strong</span> <span>connection</span> with their customers <span>through</span> personalized <span>communication.</span> As technology <span>advances,</span> <span>consumers'</span> expectations <span>also</span> <span>evolve,</span> <span>demanding</span> not only convenience but also <span>a</span> <span>sense</span> <span>of</span> <span>connection</span> <span>and</span> engagement.",
  "rewritten_plain_text": "In the modern era of rapid technological advancements, it is of utmost importance for companies to maintain a strong connection with their customers through personalized communication. As technology advances, consumers' expectations also evolve, demanding not only convenience but also a sense of connection and engagement.",
  "percentage": 67.79661016949152,
  "input_word_count": 40,
  "output_word_count": 45
}
Grammar Checker

The Grammar Checker API is a powerful tool that identifies grammatical, spelling, and punctuation errors in text and provides corrections. It is ideal for enhancing the clarity, correctness, engagement, and delivery of written content.

Request:

  • Content-Type: multipart/form-data
  • Headers: The request must include an API key in the header for authentication.
  • Body Parameters
    • input_content: (string) - The text to be checked for grammar and punctuation issues.
    • lang: (string) - The language code of the input content (e.g., en for English, es for Spanish, fr for French).

Response:

The API responds with a JSON object that includes the corrected text, a detailed analysis of the input, and specific error corrections.

Response Parameters:

  • status: (integer) - HTTP status code (200 indicates success).
  • message: (string) - A message confirming the success of the request.
  • input_text : (string) - The original text submitted for analysis.
  • incorrect_input: (string) - The input text with <span></span> tags highlighting the incorrect parts.
  • corrected_text: (string) - The text with all grammatical and punctuation corrections applied.
  • clarity: (float) - A score out of 10 indicating the clarity of the corrected text.
  • correctness: (float) - A score out of 10 indicating the grammatical accuracy of the corrected text.
  • delivery: (float) - A score out of 10 evaluating the appropriateness of tone and flow in the corrected text.
  • engagement: (float) - A score out of 10 reflecting how engaging the corrected text is.
  • errors: (array) - A list of identified errors, each containing:

    • error_type (string): The type of error (e.g., "pronoun case").
    • error_info (string): A detailed explanation of the error.
    • error_example (string): Examples showing the incorrect and correct usage.
    • replace_word (string): The incorrect word identified in the input.
    • corrected_replacement (string): The suggested correction for the error.
    • start_index (integer): The position in the input text where the error starts.
    • end_index (integer): The position in the input text where the error ends.
    • color_code (string): A color code associated with the type of error (useful for visual representation).

Grammar Checker URL

- POST - {base_url}/grammar-checker

HTTP Request Header

['x-api-key: create_your_api_key']

HTTP Request Body

[
  "input_content" => "In today’s fast-paced digital world, it’s crucial for businesses to stay connected with their customers in a personalized way. As technology evolves, so do the expectations of consumers who now seek not only convenience but also meaningful engagement.",
  "lang" => "en"
]

Response

{
  "incorrect_input": "In today’s fast-paced digital world, <span>it’s</span> crucial for businesses to stay connected with their customers in a personalized way. As technology evolves, so do <span>the expectations of consumers who</span> now seek not only convenience but also meaningful engagement.",
  "corrected_text": "In today’s fast-paced digital world, it is crucial for businesses to stay connected with their customers in a personalized way. As technology evolves, so do consumer expectations; they now seek not only convenience but also meaningful engagement.\n",
  "clarity": 9.0,
  "correctness": 9.5,
  "delivery": 8.0,
  "engagement": 7.0,
  "errors" : [
    {
      "color_code": "#4682B4",
      "corrected_replacement": "it is",
      "start_index": 37
      "end_index": 42,
      "error_example": "Incorrect: It’s time to go. Correct: It is time to go.",
      "error_info": "Contraction of 'it is' is used instead of the formal 'it is'.",
      "error_type": "contraction",
      "replace_word": "it’s",
    },
    {
      "color_code": "#4682B4",
      "corrected_replacement": "consumer expectations; they",
      "start_index": 157
      "end_index": 184,
      "error_example": "Incorrect: The expectations of consumers who now seek... Correct: Consumer expectations; they now seek...",
      "error_info": "Incorrect phrasing; wordiness and a run-on sentence.",
      "error_type": "sentence structure",
      "replace_word": "the expectations of consumers who",
      }
  ],
  "input_text": "In today’s fast-paced digital world, it’s crucial for businesses to stay connected with their customers in a personalized way. As technology evolves, so do the expectations of consumers who now seek not only convenience but also meaningful engagement."
}
;