Docs menuSchnellstart
Schnellstart
Senden Sie Ihre erste Überarbeitungsanfrage
Erstellen Sie einen API-Schlüssel im Arbeitsbereich und rufen Sie anschließend die Humanizer-, Prüf- und Zitat-Endpunkte mit diesem Schlüssel auf.
Five-minute path
From empty workspace to first humanized draft.
Keep the same sequence as the public product: create access, confirm credits, issue a key, then call the writing endpoint from your server.
Integration path
What has to happen first
Create workspace
01Google sign-in opens a private API workspace.
Add words
02Checkout and portal hooks are ready for final Stripe keys.
Generate key
03Copy the key once and store it on your server.
Call /humanize
04Send text in and receive metered output back.
Server request
Humanize endpoint
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 the AI-assisted draft you want to revise",
"language": "en",
"mode": "reduce-aigc"
}'{
"output": "The revised text...",
"words_used": 142,
"words_remaining": 2858
}Next call
Pair the result with detection or citation endpoints when your app needs review loops.
Under five minutes
Setup
Create an account
Sign in with Google, then open the workspace to manage billing, API keys, usage, and word balance.
Choose a plan or word budget
Stripe checkout and the customer portal are wired. Live product keys and prices are intentionally left for final configuration.
Create an API key
Generate a key from the workspace, copy it immediately, and send it with your API key.
Make your first request
Use the examples below to call the humanizer endpoint and inspect the response shape.
Your first API call
Replace tp_live_your_api_key with a key generated from the workspace. Requests should be sent from server-side code, not the browser.
curl -X POST https://turnitpass.com/api/v1/humanize \
-H "Authorization: Bearer tp_your_api_key" \
-H "Content-Type: application/json" \
-d '{"text":"Fügen Sie den Entwurf ein, den Sie überarbeiten möchten","language":"en","mode":"reduce-aigc","personal_terms":["TurnitPass"]}'curl -X POST https://turnitpass.com/api/v1/paraphrase \
-H "Authorization: Bearer tp_your_api_key" \
-H "Content-Type: application/json" \
-d '{"text":"Schreibe diesen Absatz in einer natürlicheren akademischen Formulierung um.","mode":"academic"}'Response
{
"output": "The humanized version of your text...",
"words_used": 8,
"words_remaining": 249992
}Beyond the first call
Workflow examples
Most integrations combine more than one TurnitPass surface. Use detector calls before or after rewriting, then use citation and bibliography endpoints when the app needs structured source output.
curl -X POST https://turnitpass.com/api/v1/detect \
-H "Authorization: Bearer tp_live_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"text": "Paste at least 50 words of writing to scan.",
"language": "en",
"source_kind": "paste"
}'curl -X POST https://turnitpass.com/api/v1/citation \
-H "Authorization: Bearer tp_live_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"input": "https://example.com/research-article",
"style": "apa"
}'Next steps
Mit Bearer-API-Schlüsseln authentifizieren
Entwickler-Anfragen erfordern API-Schlüssel, die über den TurnitPass-Arbeitsbereich generiert werden.
TurnitPass REST API
Referenz für authentifizierte Endpunkte zum Überarbeiten, Paraphrasieren, Prüfen, Zitieren, Erstellen von Bibliografien und für den API-Schlüsselstatus.