Docs

Authentication

The Training Pipes API uses bearer tokens for all authenticated endpoints. There are two types of tokens:

  • API keys — long-lived credentials you generate from the dashboard. Use these for server-side integrations.
  • Session JWTs — short-lived tokens issued by Clerk for logged-in users. The dashboard uses these automatically.

Making an authenticated request

Pass the token in the Authorization header:

curl https://api.trainingpipes.com/v1/projects \
  -H "Authorization: Bearer $TRAINING_PIPES_TOKEN"

With the SDK, pass the token when constructing the client:

import { TrainingPipes } from '@trainingpipes/sdk'

const tp = new TrainingPipes({ token: process.env.TRAINING_PIPES_TOKEN })

Rotating keys

To rotate an API key, create a new one, deploy it to your applications, then revoke the old key from Settings → API Keys. Revocation takes effect immediately.

Scoping

API keys are scoped to a single project. Requests that target a different project id will return 403 Forbidden. If you manage multiple projects, create one key per project and store them separately.

Public endpoints

A small number of endpoints are public and do not require a token:

  • GET /v1/health
  • GET /v1/config
  • GET /v1/plans