Text in, result out
The REST contract needs one text field. That makes it straightforward to add to an existing submission or editorial pipeline.
REST API / plagiarism analysis
Plagiarism Checker API for source-aware review
Add plagiarism analysis to a writing, education, or publishing product without sending reviewers to a separate tool. Submit the text from your server and bring the result back into the workflow they already use.
Use the key from a private server environment.
cURL request
curl --request POST \
--url https://api.detecting-ai.com/api/plagiarism/ \
--header "Content-Type: application/json" \
--header "Idempotency-Key: plagiarism-review-001" \
--header "X-API-Key: YOUR_API_KEY" \
--data '{
"text": "Paste the text you want to check."
}'01
POST requests to /api/plagiarism/
02
X-API-Key authentication
03
Client Idempotency-Key for recoverable retries
04
One required text field
05
Feature-specific word balance
Keep the source in the conversation
Similarity is useful when the reviewer can inspect why it appeared
The API gives your product a plagiarism result and usage data. Your interface should pair that result with the submitted passage, available source context, and the rules that matter to the reviewer.
Server-side by default
Keep the customer key out of the browser and return only the report data your application is prepared to explain.
Review before action
Treat overlap as a lead for source checking. Citation, permission, and policy still determine what a match means.
Request contract
The request body has one job
Send the complete text you want checked as a JSON string. Handle document parsing, access control, and any submission metadata in your own application.
| Field | Type | Required | What it does |
|---|---|---|---|
| text | string | Yes | The text you want the plagiarism service to analyze. |
Inspect the returned result before shaping the UI
The result field carries the analysis and words_processed records usage. Keep the raw response in a private test log until your mapping handles both normal and empty findings.
Example response
{
"result": "Plagiarism analysis is returned here",
"words_processed": 8
}Integration flow
Start with a small, traceable review loop
A clear integration keeps the submitted text, analysis, and reviewer action connected.
- 1
Create a private server call
Store the API key as a secret and accept text only from users and systems your application already authorizes.
- 2
Submit realistic documents
Persist a unique Idempotency-Key, then test realistic essays, articles, listings, and quoted or cited material. Reuse the key only for an exact retry.
- 3
Build the review state
Show enough source and passage context for a person to understand a match before marking, rejecting, or escalating it.
Good fits
Designed for queues where originality already matters
The API belongs beside the document and its history. That makes it easier to investigate a match and avoids turning a percentage into a final judgment.
A match needs context
Quoted text, references, standard phrases, and licensed material can all create overlap. Review what matched and why before taking action.
Assignment review
Bring a plagiarism result into the same screen as the submission, citation details, rubric, and instructor notes.
Editorial intake
Check contributed work before publication and send meaningful overlap to an editor for source review.
Catalog content
Review repeated product or marketplace descriptions before they are added to a large catalog.
Internal quality checks
Run authorized text through a private backend and keep the key separate from the browser interface.
API FAQ
Practical answers before you ship
Start with a server-side request, log the response shape, then add the result to your existing review flow.
What endpoint does the Plagiarism Checker API use?+
Send a POST request to https://api.detecting-ai.com/api/plagiarism/. The JSON body has a required text field; send X-API-Key and persist a stable Idempotency-Key so retries are recoverable.
What does a successful response contain?+
The response contains the plagiarism result and words_processed. Inspect the result in a test environment before mapping it into your own report interface.
Does a match automatically mean plagiarism?+
No. Matching language may be quoted, licensed, common, properly cited, or part of a reference list. Your workflow should let a reviewer inspect the source and context.
Should the API key be sent from the browser?+
No. Keep the key in a trusted server environment and call the plagiarism endpoint from there. A browser bundle or public repository cannot protect a private key.
How is plagiarism usage counted?+
Usage is based on the input word count and comes from the plagiarism balance on the API subscription. Successful responses include words_processed.
Build the first request
Test the API with cited and uncited samples
A useful trial includes clean text, common phrases, quotations, and a known copied passage so your team can design the right review states.