Docs menuOverview

DocumentationQuickstart to reference

Documentation Développeurs

Documentation API TurnitPass

Commencez avec les clés API, appelez les endpoints de révision, vérification, paraphrase, citation et bibliographie, puis intégrez TurnitPass dans votre application.

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

POST /api/v1/humanize

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"}'

response

200 OK

{
  "output": "Your humanized text...",
  "words_used": 6,
  "words_remaining": 249994
}

TurnitPass also exposes paraphrase, rewrite, detector, citation, bibliography, and status endpoints from the same API-key flow.

Route map

Explore the docs

Démarrage rapide

Créez une clé API depuis l’espace de travail, puis appelez les endpoints d’écriture, de vérification et de citation avec la même clé.

Authentification

Les requêtes de développement utilisent des clés API générées depuis l’espace de travail TurnitPass.

Référence API

Référence pour les endpoints authentifiés de révision, paraphrase, vérification des signaux, citation, bibliographie et statut de clé.

Changelog

Modifications récentes apportées à l’humaniseur, au détecteur, aux outils d’écriture, à la facturation et aux interfaces API.

Faites votre première requête de révision

Create a key and make the first request.

API REST TurnitPass

Review endpoints, parameters, limits, and response shapes.

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

Endpoints principaux

Réviser

POST/api/v1/humanize

Atténue les signaux de rédaction IA tout en préservant le sens.

Paraphraser

POST/api/v1/paraphrase

Réécrit et peaufine le texte selon plusieurs modes.

Vérifier

POST/api/v1/detect

Retourne un score estimé, le niveau de risque et les signaux de style.

Citations

POST/api/v1/citation

Formate les métadonnées de sources DOI, URL ou manuelles.

Production checklist

Server-side calls

Never expose API keys in client bundlesCall TurnitPass from your backend, worker, queue, or protected server action.

Retry behavior

Retry network failures, not validation failuresHandle 4xx responses as user or payload issues and reserve retries for transient 5xx/network errors.

Word budgets

Show remaining balance before heavy flowsUse the status endpoint to decide whether to queue a job, ask for upgrade, or split a document.

Billing setup

Stripe secrets are final configurationThe checkout, portal, and webhook surfaces are wired; live keys and price IDs are intentionally left for deployment.

For product integrations, keep one TurnitPass key per environment. Production, staging, and local development should be revocable independently.