Skip to main content
A project is the boundary for one service: its ingest, logs, traces, incidents, dashboards, and API keys. Use this API to find a project ID and to check that the project receives data.

​
List projects

​
Get one project

​
Check project setup

This read-only operation requires project:read. It returns the project id, name, platform, data region, collector URL, ingest-key state (missing, unused, or used), and recent error or log event state (pending, verified, or unavailable). The signal check covers the last 24 hours. A verified event includes an opaque receipt id, kind, and observed time. No API key value or event payload is returned. Use squasher projects setup <project_id> or the MCP Code Mode operation projects.setup for the same status. If the status is pending, check the key’s events:ingest scope, the project id, and the collector URL, then send a safe test event. If the status is unavailable, retry verification before changing the integration. An ingest-only key cannot read this endpoint. Sign in to the CLI or MCP with OAuth, or use a separate key with project:read. Keep the ingest key limited to telemetry. Typical project fields include:
  • id
  • organization_id
  • name
  • slug
  • platform
  • framework
  • max_events_per_minute
  • created_at
  • updated_at
team_id is still returned as a deprecated compatibility alias for organization_id.

​
Agent handoff

Project discovery is usually the first read-only step:
Use squasher projects list, squasher projects get <project_id>, or MCP search("projects.list").