Skip to main content
A log connector is one managed log source for a project, such as a Vercel log drain. Every connector gets its own ingest key, so you can rotate or revoke one source without touching the rest of the project.

Authentication

All endpoints in this section require a Squasher API key with project:read or project:write access.

Connector catalog

Returns the connector profiles currently supported by Squasher.

Response

You can pass either the canonical connector_key or one of the returned aliases when creating or onboarding a connector.

List project connectors

Response

Create a connector

Request body

Response

The raw_key is only returned on create and rotate.

Onboard a connector

Creates the connector and returns the same setup material plus API, CLI, and MCP guidance for self-serve onboarding.

Request body

Response

For OTLP connectors, use the managed key with both:
  • https://ingest.squasher.ai/v1/logs
  • https://ingest.squasher.ai/v1/traces

Agent handoff

Use managed connectors when an agent is onboarding a log source:
CLI equivalents live under squasher log-connectors .... MCP clients should call search("logConnectors.onboard") or search("logConnectors.verify"), then execute the selected operation.

Get one connector

Returns the current connector record.

Update a connector

Request body

Returns the updated connector record.

Verify a connector

Marks the connector as verified and returns the updated connector record.

Rotate a connector key

Returns a fresh managed ingest key plus updated setup material.

Response

Delete a connector

Deletes the connector record and revokes its managed ingest key.