To process file, send a POST request to the https://api.groupdocs.cloud/v2.0/rewriter/{task}/document GroupDocs.Rewriter Cloud REST API endpoint, where task means what you want to do: detect, paraphrase, simpllify or summarize. To authorize the request, pass the access token in Authorization header (Bearer authentication).
The link to file and processing parameters are provided in JSON format in the request body.
How the result shoud be saved, as file, as archive or both.
outputFormat
Format of the paraphrased file.
summarizationDegree
Summarization degree, accepted values Off, Medium and High.
format
File format.
minLength
Minimal length of files textual content to apply summarization.
Note
If the processed file is very long, you may encounter an error when calling via cURL in a shell command. Use the getconf ARG_MAX command to check the maximum length of the command arguments (in bytes).
Evaluation mode
To use GroupDocs.Rewriter Cloud REST API in evaluation mode, send a POST request to the endpoint https://api.groupdocs.cloud/v2.0/rewriter/{task}/document/trial.
This endpoint does not use the Authorization header, so there is no need to generate an access token. All other parameters remain the same as in regular text requests.
Return value
If successful, this method returns JSON with a unique identifier (value of the id property) of the request in the queue:
Otherwise, it returns a HTTP status code corresponding to the error.
What’s next
Processing will take a few seconds, depending on the size of the text and the current GroupDocs.Rewriter Cloud load. See the article Fetching results for information on how to get results from the server.