Developer docs API integration

Send your first error to StackLogger

Connect your application in a few minutes. Create an app, grab its credentials, then forward errors from your application boundary to the ingestion API.

5 minute setupREST APIAny framework

Quickstart

There are five steps between a fresh account and your first tracked error.

01

Create an account

Start with a free StackLogger account. No credit card is required during the beta.

Create your account
02

Create an app

From the dashboard, select New app. Give it a name that maps to the service or frontend you want to monitor, such as checkout-web or payments-api. Save the application's domain too, for example https://your-domain.com; StackLogger uses it to verify incoming events.

03

Activate your app

Open the app you just created and activate it. An active app is ready to receive events and appear in your error dashboard.

Why activation? Activation is the final switch that tells StackLogger this app is ready for production traffic.
04

Get your credentials

In your app's Integration tab, copy the application key and confirm the saved domain. Keep the key on your server or in a protected runtime environment—never expose it in client-side source.

Treat keys like passwords. If one is exposed, rotate it from the same credentials screen.
05

Connect your error boundary

Catch unhandled errors at the boundary your framework provides, then send a structured event to the ingestion endpoint. Include both the X-StackLogger-Key and an Origin or Referer whose origin exactly matches the domain saved for the application. Browser requests send Origin automatically; server-side clients should set it explicitly.

POST /v0.1/errors/ingest
curl -X POST https://ingest.stacklogger.io/v0.1/errors/ingest \
  -H "Content-Type: application/json" \
  -H "X-StackLogger-Key: YOUR_APPLICATION_KEY" \
  -H "Origin: https://your-domain.com" \
  -d '{
    "app_id": "YOUR_APP_ID",
    "error": {
      "message": "Something went wrong",
      "stack": "Error: Something went wrong\n    at checkout (checkout.js:42:11)",
      "url": "https://your-app.com/checkout",
      "environment": "production"
    }
  }'

SDKs

Install the SDK for your stack to initialize StackLogger with your application key and start capturing errors.

npm install @stacklogger/react

import { StackLogger } from '@stacklogger/react'

StackLogger.init({
  apiKey: import.meta.env.VITE_STACKLOGGER_API_KEY,
  environment: import.meta.env.MODE,
})
Read the React SDK README

Framework notes

The API is framework-agnostic, so you can integrate any stack directly when a framework-specific SDK is not available.

1

React / Next.js

Use your root error boundary or error.tsx to capture the error, then call the ingestion endpoint from a server-safe function.

2

Node.js services

Wrap your request handlers or process-level error hooks and forward the normalized error payload.

3

Other frameworks

Find the framework’s global error boundary or exception hook, normalize the error, and make the same POST request.

Need help with your stack?

Tell us which framework you use. We're prioritizing SDKs based on what the community needs most.

Request an SDK
Next: once your first event arrives, open the StackLogger dashboard to inspect the full stack trace and start resolving it.