Overview

The SeeStack ingestion API accepts telemetry data over HTTP. All endpoints require the X-SeeStack-Key header for authentication and return 202 Accepted on success.

Endpoints

Errors

Ingest application errors and exceptions

Logs

Ingest structured application logs

HTTP Requests

Ingest HTTP request telemetry in batches

Session Replay

Ingest DOM and interaction events

Heartbeat

Send cron job heartbeat pings

Authentication

All endpoints require the X-SeeStack-Key header with your raw API key:

X-SeeStack-Key: seestack_live_abc123xyz...

The key is validated and the associated project is resolved automatically. You do not need to send a project ID (except for the HTTP requests endpoint).

Response Format

Most endpoints return a standard envelope:

{
  "success": true,
  "data": { ... },
  "meta": {
    "requestId": "uuid",
    "timestamp": "2026-03-31T12:00:00.000Z"
  }
}

The /ingest/v1/http-requests and /ingest/v1/heartbeat endpoints return raw JSON objects instead of the standard envelope.