Skip to main content
This guide walks you through sending your first log entry to Peeng. You only need an HTTP client — no SDK, no extra dependencies. By the end you will have a working request that returns 202 Accepted and a log visible in the Peeng dashboard.
1

Create a project and API key

Go to https://peeng.dev/register and sign up or sign in. Create an organization and a project if you haven’t already, then navigate to Settings → API Keys and generate a new key.Your key looks like this:
Copy your key now — it is only shown once at creation time. If you lose it, you will need to regenerate it. See Authentication for details on test vs. live keys and key rotation.
2

Send a log

Every integration path — SDK or raw HTTP — calls the same endpoint: POST https://api.peeng.dev/v1/logs. Pick whichever example fits your stack:
A successful request returns 202 Accepted with the following body:
The accepted count reflects the number of log entries Peeng queued from your request.
3

Check the dashboard

Open the log explorer in your Peeng project. Your log appears within a few seconds of the request completing. You can filter the explorer by:
  • Levelinfo, warn, error, debug
  • Service — the service field you set in the log body
  • Status code — the statusCode field
  • Request ID — a requestId you attach to correlate logs across a single request
  • User ID — a userId you attach to trace activity for a specific user
4

(Optional) Install an SDK

For production use, the official SDKs handle batching, automatic retries on transient failures, and idempotency — so you never block your application waiting for a log to flush, and you never lose entries during a brief network hiccup.
See the JavaScript / TypeScript SDK and Python SDK pages for full setup and configuration guides.

Next steps

Authentication

Learn how test vs. live keys work, and how to rotate a key safely.

API Reference

Every field and option that POST /v1/logs accepts.