Skip to content
TurnitPass
DevelopersAPI v1Get an API key
Browse documentation

DevelopersDevelopers

TurnitPass developer hub

API docs, keys, usage limits, and billing support for embedding TurnitPass in editors, LMS tools, and internal workflows.

REST API v1

Start from the workflow you need

Developer hub

Production path

Create a key, call the endpoint, track usage.

TurnitPass keeps the developer path close to the product workflow: account-owned keys, metered requests, word balance, and docs that map to live routes.

01

Create API key

Generate a named key from the workspace and copy it once.

02

Send Bearer request

Call humanizer, detector, paraphrase, citation, or bibliography routes.

03

Review usage

Requests roll up to word balance, endpoint logs, and future billing limits.

v1
POST/humanizePOST/paraphrasePOST/detectPOST/citation
request
POST /humanize
curl -X POST /api/v1/humanize
-H "Authorization: Bearer $KEY"

200 OK

response

142

words used

2,858

remaining

workspace

Keysscoped
Meteringaccount
BillingPlan-aware
Limitsplan-aware

Private by default

Keys stay hashed and account-scoped.

API Surface

Core endpoints

Authenticated

Bearer API keys

Metered

word balance

Product-ready

billing hooks

Revise

POST/api/v1/humanize

Revise AI-assisted text while preserving meaning.

Paraphrase

POST/api/v1/paraphrase

Rewrite and polish text in multiple modes.

Detect

POST/api/v1/detect

Return AI-writing signal estimates and revision notes.

Citations

POST/api/v1/citation

Format DOI, URL, or manual source metadata.

Use cases

What developers are building

The API follows the same TurnitPass workflow writers use in the browser: humanize, detect, rewrite, paraphrase, cite, and track usage.

01POST /api/v1/humanize

Content platforms

Humanize AI-assisted drafts before publishing, then expose detector feedback and citation cleanup inside your editor.

02POST /api/v1/paraphrase

Writing tools

Add paraphrase, rewrite, and AI-writing review to existing document workflows without building the model layer yourself.

03POST /api/v1/detect

Review workspaces

Send submissions through detector endpoints, store review notes, and show reviewers the signals behind each estimate.

04POST /api/v1/citation

Research workflows

Format citation and bibliography output for source-heavy products, student tools, and academic writing assistants.

Production detail

Limits, billing, and reliability

These are the operational rules client apps should design around before enabling TurnitPass for real users.

Authentication

Bearer API key

Workspace API keys are shown once when created and can be revoked without changing Google login.

Transform limit

Per-request length

Humanize, paraphrase, and rewrite endpoints share the transform word limit and deduct successful requests from balance.

Detection limit

5,000 words/request

Detector requests support longer review inputs and return estimates, review notes, and signal details.

Rate limits

50 req/min/key

Transform, detector, and status endpoints default to 50 requests per minute per key; citation routes allow 100.

Billing path

Plan-aware

Checkout, portal, webhooks, word balance, and plan limits stay in sync with your subscription.

Failure handling

Charge on success

Transform words are consumed after a successful engine response, so failed validation or engine errors do not spend words.

Production notes

Private by default. API usage is tied to a user-owned key. Requests are metered for usage limits, account access, and future team controls.
Integrated billing. Billing workflows, customer portal access, and plan-specific limits can be configured as your product grows.

Before launch

Ship checklist

1

Create test key

Generate a workspace API key and confirm the prefix appears only once.

2

Run core calls

Call humanize, detect, paraphrase, citation, bibliography, and status with the same Bearer token.

3

Handle errors

Map invalid_api_key, rate_limited, insufficient_words, and validation errors in your client.

4

Set billing

Choose a plan and manage checkout, portal access, and invoices from the workspace.

Next, make it part of your workflow.Continue reading