Docs

Reference for the eight official SDKs and the HTTP API underneath them. Pick your language, or skip the SDK and post the JSON yourself.

SDKs

Each page covers installation, initialisation, one log, one metric and the questions people actually ask. Every snippet is copied from the SDK README it links back to.

Node.js npm install @logdash/node Python pip install logdash Go go get github.com/logdash-io/go-sdk/logdash logo_NET .NET dotnet add package Logdash Java implementation 'io.logdash:logdash:0.2.0' file_type_rust Rust cargo add logdash Ruby gem install logdash PHP composer require logdash/php-sdk

Raw HTTP API

Every SDK is a wrapper around a handful of endpoints. If your language has no SDK, or you just want to prove the pipe works, curl it. Logs and metrics authenticate with your project API key in a project-api-key header.

POST /logs
curl -X POST "https://api.logdash.io/logs" \
-H "project-api-key: <your-api-key>" \
-H "Content-Type: application/json" \
-d '{"message": "Application started successfully", "level": "info", "createdAt": "2026-09-04T09:41:00.000Z", "sequenceNumber": 0}'
PUT /metrics
curl -X PUT "https://api.logdash.io/metrics" \
-H 'project-api-key: <your-api-key>' \
-H 'Content-Type: application/json' \
-d '{"name": "users", "value": 0, "operation": "set"}'

Heartbeats are the exception. A push monitor exposes a public endpoint with no key and no body, so the URL is the secret. Call it on a schedule and Logdash marks the monitor down when the calls stop.

POST /ping/<monitorId>
curl -X POST "https://api.logdash.io/ping/<monitorId>"

More

Self-hosting What runs on your own machine today, and what still stops a production deployment.
Guides Logging, metrics and monitoring explained, with the plan limits that apply to each.