Docs menuAuthentification

AuthenticationBearer keys, shown once

Authentification

S’authentifier avec des clés API Bearer

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

Auth console

Keep API keys out of the browser.

TurnitPass API calls use a workspace-owned Bearer key. The key belongs in server-only code, while the dashboard remains the place to create, rotate, revoke, and inspect usage.

Key guardrails

How to keep access safe

4 checks

Server only

Send keys from backend routes, workers, jobs, or secure server actions.

Shown once

Copy the generated key immediately and store it in your secret manager.

Rotate safely

Deploy the replacement key before revoking the old production key.

Account scoped

Usage rolls up to the workspace word balance and billing controls.

Bearer request

Header contract

private by default

request

Bearer

fetch('https://turnitpass.com/api/v1/humanize', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer tp_live_your_api_key',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({ text: draft, language: 'en' })
})

failed auth

401

{
  "error": "Invalid or revoked API key.",
  "code": "invalid_api_key"
}

01Generate in workspace

02Store in secrets

03Call from server

04Rotate or revoke

API keys

Envoyez `Authorization: Bearer tp_your_api_key` avec chaque requête. Les clés sont affichées une seule fois, stockées de façon sécurisée et peuvent être révoquées depuis l’espace de travail.

Authorization header

Bearer

Authorization: Bearer tp_live_your_api_key
Content-Type: application/json

POST /api/v1/humanize

Keys are shown once when created and can be revoked from the workspace without changing the Google login account.

Managing keys

Create

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

Revoke

Disable a key instantly. Revoked keys cannot be used for new requests.

Rate limits

Each key can be rate-limited independently while usage rolls up to the account.

Billing

All keys share the account word balance and subscription limits.

Workspace owned

Key lifecycle

Create a named key

Use a name that describes the environment or app surface, such as Production backend, Staging worker, or Internal QA.

Copy it once into a secret store

TurnitPass displays the key only at creation. Store it in your deployment provider, CI secret manager, or local .env file.

Watch usage through status and billing

All keys share the account word balance, while individual key names make it easier to find which integration is active.

Rotate before revoking

Create a replacement key, deploy it, confirm traffic is healthy, then revoke the old key from the workspace.

Environment setup

Store TurnitPass keys as server-only secrets. The examples below use generic names so they can fit Next.js, Workers, server jobs, or any backend runtime.

.env

server only

TURNITPASS_API_KEY=tp_live_your_api_key
TURNITPASS_API_BASE_URL=https://turnitpass.com/api/v1

Local development

.env.local or local secret managerUse a non-production key with a small word budget and clear name.

Preview deploys

Staging keyKeep preview traffic separate so test jobs do not consume production usage unexpectedly.

Production

Backend-only secretRead the key only from trusted server code. Never pass it to the browser.

Security best practices

Server-side only

Never expose keys in browser codeUse keys from backend services, jobs, or secure server routes.

Environment variables

Use TURNITPASS_API_KEYAvoid hardcoding live keys into source control or client bundles.

Rotate keys

Create a replacement before revokingUse separate keys for production, staging, and development.

Compromise response

Revoke immediatelyCreate a new key from the workspace if a key is leaked.

Authentication errors

Missing header

No Authorization header provided

Bad format

Header does not start with Bearer

Invalid key

Key not found, revoked, or malformed

Too many failures

Repeated failed auth attempts can be rate-limited

401 response

JSON

{
  "error": "Invalid or revoked API key.",
  "code": "invalid_api_key"
}

Next steps

Démarrage rapide

Make the first humanization request.

Référence API

Review endpoints, parameters, and response formats.

fetch('https://turnitpass.com/api/v1/humanize', { method: 'POST', headers: { Authorization: 'Bearer tp_live_your_api_key', 'Content-Type': 'application/json' }, body: JSON.stringify({ text: draft, language: 'en' }) })

API keys

Authorization header

Bearer

Authorization: Bearer tp_live_your_api_key
Content-Type: application/json

POST /api/v1/humanize

Keys are shown once when created and can be revoked from the workspace without changing the Google login account.

Managing keys

Create

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

Revoke

Disable a key instantly. Revoked keys cannot be used for new requests.

Rate limits

Each key can be rate-limited independently while usage rolls up to the account.

Billing

All keys share the account word balance and subscription limits.

Key lifecycle

Create a named key

Use a name that describes the environment or app surface, such as Production backend, Staging worker, or Internal QA.

Copy it once into a secret store

TurnitPass displays the key only at creation. Store it in your deployment provider, CI secret manager, or local .env file.

Watch usage through status and billing

All keys share the account word balance, while individual key names make it easier to find which integration is active.

Rotate before revoking

Create a replacement key, deploy it, confirm traffic is healthy, then revoke the old key from the workspace.

Environment setup

Store TurnitPass keys as server-only secrets. The examples below use generic names so they can fit Next.js, Workers, server jobs, or any backend runtime.

.env

server only

TURNITPASS_API_KEY=tp_live_your_api_key
TURNITPASS_API_BASE_URL=https://turnitpass.com/api/v1

Local development

.env.local or local secret managerUse a non-production key with a small word budget and clear name.

Preview deploys

Staging keyKeep preview traffic separate so test jobs do not consume production usage unexpectedly.

Production

Backend-only secretRead the key only from trusted server code. Never pass it to the browser.

Security best practices

Server-side only

Never expose keys in browser codeUse keys from backend services, jobs, or secure server routes.

Environment variables

Use TURNITPASS_API_KEYAvoid hardcoding live keys into source control or client bundles.

Rotate keys

Create a replacement before revokingUse separate keys for production, staging, and development.

Compromise response

Revoke immediatelyCreate a new key from the workspace if a key is leaked.