Skip to main content

Intro

The Projects API lets you manage LangWatch projects via REST. When you create a project, a project-scoped service API key is automatically generated and returned, ready to use for sending traces. This API is designed for service-to-service automation (e.g. an internal tool that scaffolds new projects), not for end-user access.

Authentication

The Projects API requires an organization-level API key (created in Settings > API Keys). Pass it as a Bearer token:
Project API keys (X-Auth-Token) cannot be used here, because they lack organization context.

Endpoints

Dashboards boards

These routes read the boards of the Dashboards area in one project. Unlike the routes above, they take the project API key in the X-Auth-Token header, not an organization key. A board in another project answers 404.

Moving a Project to Another Team

You can move a project to a different team by including teamId in the PATCH request:
Moving a project changes its access boundary. Members who had access through the source team will lose inherited access, while members of the destination team will gain it. Project-level access overrides are preserved.

Typical Flow

  1. Create an admin API key in Settings > API Keys with organization:manage permission
  2. Call POST /api/v1/projects with the project name and either an existing teamId or a newTeamName
  3. Store the returned serviceApiKey and project id
  4. Use both values in your application:
The serviceApiKey is shown only once in the create response. Store it securely, because you cannot retrieve it later.
Last modified on October 26, 2026