Docs menuAPI 參考
API ReferenceTyped request and response
API 參考
TurnitPass REST API
自然化改寫、改寫潤飾、AI 檢測、文獻引用、參考文獻和 API 金鑰狀態端點參考。
Reference console
Start with the route, payload, and response shape.
The full reference covers every endpoint below. The console shows the contract developers need first: Bearer auth, JSON input, metered output, and status checks.
request
POST
fetch('/api/v1/humanize', {
method: 'POST',
headers: {
Authorization: 'Bearer tp_live_your_api_key',
'Content-Type': 'application/json'
},
body: JSON.stringify({
text: 'Paste the draft here',
language: 'en',
mode: 'reduce-aigc'
})
})response
200 OK
{
"output": "The revised text...",
"words_used": 142,
"words_remaining": 2858,
"status": "succeeded"
}meteredloggedJSON
POST
/api/v1/humanizePOST
/api/v1/paraphrasePOST
/api/v1/detectPOST
/api/v1/citationGET
/api/v1/statusAuthBearer API key
TransformPOST /humanize
ReviewPOST /detect
StatusGET /status
POST
v1/api/v1/humanize降低提交文字中的 AI 痕跡。支援 reduce-aigc、reduce-both、paraphrase、academic-polish 等模式。
POST
v1/api/v1/paraphrase按標準、流暢、正式、學術、簡潔、創意、擴寫或縮寫模式改寫文字。
POST
v1/api/v1/detect為貼上文字或解析後的檔案回傳分數、風險等級、元資料和 AI 寫作訊號。
POST
v1/api/v1/citation將 DOI、URL 或手動來源格式化為 APA、MLA、Chicago、IEEE、Harvard、GB/T 等格式。
GET
v1/api/v1/status查看金鑰名稱、剩餘字數和請求限制。
Parameters and options
Rate limits and request limits
Error handling
Error responses use JSON with error,code, and human-readable message fields where possible.
error response
JSON
{
"error": "Text exceeds word limit. Maximum 1,000 words allowed.",
"code": "word_limit_exceeded",
"max_words": 1000,
"current_words": 1234
}The Stripe and Google credentials are configuration points. The API surfaces, auth flow, and persistence are implemented so live credentials can be added without redesigning the product.
Examples
Humanize example
JSON
POST /api/v1/humanize
{
"text": "請把這段 AI 草稿改得更自然。",
"language": "zh_TW",
"mode": "reduce-aigc"
}Multi-endpoint example
JSON
POST /api/v1/detect
{
"text": "需要檢查的文字",
"language": "zh_TW",
"source_kind": "paste"
}