Docs menuOverview

DocumentationQuickstart to reference

Documentación técnica

Documentación de API de TurnitPass

Comienza con claves de API y llama a los endpoints para revisar, parafrasear, comprobar señales, crear citas y generar bibliografías dentro de tu propio software.

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

Inicio rápido

Crea una clave de API en la consola y luego llama a los endpoints de redacción, comprobación y citas con la misma clave.

Autenticación

Las solicitudes de desarrollo utilizan claves de API generadas desde la consola de control de TurnitPass.

Referencia de API

Referencia para los endpoints autenticados de revisión, paráfrasis, comprobación de señales, citas, bibliografía y estado de claves.

Historial

Cambios recientes en revisión de textos, comprobación de señales, herramientas de redacción, facturación y API.

Realiza tu primera solicitud de revisión

Create a key and make the first request.

API REST de 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 principales

Revisar

POST/api/v1/humanize

Disminuye patrones de escritura tipo IA conservando el significado.

Parafrasear

POST/api/v1/paraphrase

Reescribe y perfecciona texto en múltiples modos.

Comprobar

POST/api/v1/detect

Devuelve puntajes estimados, nivel de riesgo y patrones de escritura.

Citas

POST/api/v1/citation

Formatea metadatos de fuentes DOI, URL o ingresados manualmente.

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.