The TigerTrust REST API is the same surface the dashboard uses. This reference documents only what customers script against — a small set of core operations. The full machine-readable contract for every endpoint (across CLM, PAM, Secrets Manager, and NHI Governance) lives in the OpenAPI spec.
Internal machine-to-machine surfaces (Collector’s agent-facing endpoints, staff / operator routes, dashboard-only session routes) are not exposed to customer API keys and are intentionally omitted from this reference.

Base URL

https://api.<your-domain>
Every endpoint documented here is relative to that base and prefixed with /api/.

What’s in this reference

Authentication

Obtain an API key, send it via X-API-Key or Authorization: Bearer, and scope it to a workspace.

Pagination & errors

Response envelope, standard error codes, page/limit conventions.

Certificates

List, issue, renew, revoke, deploy — the CLM surface.

Certificate Authorities

Manage internal PKI and external CAs.

Discovery

Trigger scans, review findings, import discovered certs.

Attestation

TPM-gated device issuance.

Webhooks

Signed HTTP callbacks for workspace events.

OpenAPI 3.1

Machine-readable spec covering every operation across CLM, PAM, SM, and NHIG — codegen-ready.

Conventions

All responses are JSON, all timestamps are ISO 8601 in UTC, and every request/response body uses camelCase field names.
  • Requests to POST / PUT / PATCH use application/json (unless documented otherwise — e.g. certificate downloads return application/x-pem-file).
  • Successful responses wrap data in { "data": ... } for single resources and { "data": [...], "pagination": {...} } for lists. Full schema in Pagination & errors.
  • Errors return { "error": { "code": "...", "message": "...", "details": {...} } }.

Workspace scope

API keys are issued per workspace and cannot cross workspace boundaries. See Authentication.

Rate limits

Public keys: 300 requests/minute (500 burst). Retry-header contract in Pagination & errors.

Everything else

For endpoints not documented above — PAM sessions, SM engines, NHIG identities, IoT devices, code-signing operations, SSH key lifecycle, etc. — the source of truth is the OpenAPI spec. It’s the same file the platform generates its Go/Python/TypeScript SDKs from, so what’s in the spec is what actually works.

Not documented anywhere

  • Collector routes used by the field agent (/collector/*). Machine-to-machine internal API — auth is a dedicated agent key (ak_...) minted from the dashboard.
  • Staff / operator routes (/api/staff/*). Reserved for TigerTrust operators.
  • Session-cookie–only routes used by the dashboard when it forwards a browser session.