🔑

Projects & API Tokens

Project-scoped configuration and authentication

A Project is a workspace that encapsulates configuration and data for a single application or client. You can create multiple projects. Each project has its own categories, schemas, moderation settings, and tokens.

📁Projects

Use projects to separate products, client workspaces, or sandboxes. Configuration and access are isolated per project.

Typical Use Cases

  • • One project per application or microservice
  • • One project per customer (multi-tenant isolation)
  • • Temporary projects for testing or demos
  • • Optional: separate projects for dev/stage/prod if you want strict isolation

What a Project Contains

Project identity & settings

Each project has a Name and a Project ID (slug). The Project ID appears in Console URLs (e.g., /console/<project_id>) and can be changed from Console → Settings. Renaming affects only the display name; updating the Project ID changes the URL segment for the project in Console.

Isolation model

Categories, schemas, automated/manual settings, submissions, and tokens are scoped to one project and are not shared across projects. Deleting a project removes its configuration and invalidates all of its tokens.

🔒API Tokens

Tokens authenticate your API requests. A token is scoped to exactly one project and inherits that project's settings.

Capabilities

  • • Named tokens — Label tokens by service or environment
  • • Instant revocation — Disable compromised tokens immediately

What you can do in Console → Tokens

  • • List tokens — See existing tokens with their names
  • • Create token — Provide a descriptive name; token becomes immediately usable
  • • Reveal/hide token value — Temporarily reveal a token to copy it
  • • Copy to clipboard — One-click copy for integration
  • • Delete token — Immediately revokes access for that token

Generate a Token

  1. 1. Open Console → Tokens in the target project
  2. 2. Click Generate Token
  3. 3. Provide a descriptive name (e.g., "checkout-service-prod")
  4. 4. Copy and store it securely (environment variables)

Token rotation

  1. 1. Create a new token and deploy it to your services
  2. 2. Verify it’s used in production
  3. 3. Revoke the old token

Use the Token

Include your API token in the Authorization header for all API requests:

GET https://api.outharm.com/health
Authorization: Bearer YOUR_TOKEN_HERE

Best Practices

Security

  • • Store tokens in server-side environment variables
  • • Rotate and revoke tokens regularly
  • • Do not embed tokens in client-side code

Organization

  • • Use meaningful names: service-environment
  • • Prefer separate tokens per service

Ready to Get Started?

Create your first project and generate API tokens to start building with Outharm's content moderation platform.

Console Walkthrough

Learn how to manage projects and tokens

→

Quick Start Guide

Step-by-step project setup

→

Related Documentation