Docs menuOverview
开发者文档
TurnitPass API 文档
从 API 密钥开始,调用自然化改写、改写润色、AI 检测、文献引用和参考文献端点,把 TurnitPass 接入你的写作产品。
One request
Quick example
Send text to the humanizer endpoint with a Bearer API key. The response returns the transformed output, words used, and the remaining word balance for the key owner.
curl -X POST https://turnitpass.com/api/v1/humanize \
-H "Authorization: Bearer tp_live_your_api_key" \
-H "Content-Type: application/json" \
-d '{"text":"Paste your draft here","language":"en","mode":"revise"}'{
"output": "Your humanized text...",
"words_used": 6,
"words_remaining": 249994
}Route map
Explore the docs
快速开始
在工作台创建 API 密钥,然后用同一个 Bearer 令牌调用改写、AI 检测和引用接口。
认证
开发者请求使用 TurnitPass 工作台生成的 API 密钥。
API 参考
自然化改写、改写润色、AI 检测、文献引用、参考文献和 API 密钥状态端点参考。
更新日志
自然化改写、AI 检测、写作工具、账单和 API 的近期变化。
Production flow
Request lifecycle
Every TurnitPass API call follows the same product path: authenticate the key, validate the payload, run the writing or citation workflow, meter usage, and return a response shape that can be stored by your product.
Authenticate the API key
Send an API key generated from the workspace. Revoked, malformed, or missing keys fail before text processing starts.
Validate text, language, and limits
Transform requests enforce word ranges, detector requests enforce longer scan limits, and citation requests validate style and source input.
Run the workflow
Humanize, paraphrase, rewrite, detect, citation, and bibliography routes reuse the same server-side behavior as the public tools.
Record usage and return output
Successful calls return output plus usage metadata such as words used, remaining balance, status details, or formatted citation exports.
API Surface
Core endpoints
Revise
/api/v1/humanizeRevise AI-assisted text while preserving meaning.
Paraphrase
/api/v1/paraphraseRewrite and polish text in multiple modes.
Detect
/api/v1/detectReturn AI-writing signal estimates and revision notes.
Citations
/api/v1/citationFormat DOI, URL, or manual source metadata.