Developer Docs

SDK & API Reference

Install the published Node.js SDK or use direct HTTP ingestion. Other SDK package registries are coming soon.

Developer Docs

Quick Start Guide

Get Jidar SecOps collecting events from your infrastructure in under 5 minutes. Send logs via our API or SDKs.

Authentication

All API requests require a Bearer token. Generate one from your dashboard under Settings → API Keys.

          # Set your API key as an environment variable

          export JIDAR_API_KEY="<server-side-api-key>"

TypeScript / Node.js

Published npm · @jidar/sdk v0.1.0

Package registry coming soon

Package registry coming soon

Package registry coming soon

Package registry coming soon

Package registry coming soon

TypeScript / Node.js SDK

Package: @jidar/sdk
Version: 0.1.0
npm: https://www.npmjs.com/package/@jidar/sdk
Requires Node.js 18 or newer.

npm install @jidar/sdk

          import { Jidar } from "@jidar/sdk";

          const jidar = new Jidar({

            apiKey: process.env.JIDAR_API_KEY,

            sourceId: "backend-api"

          });

          await jidar.captureFailedLogin({

            email: "user@example.com",

            ip: "203.0.113.42",

            userAgent: "Example",

            reason: "invalid_password"

          });
          
          await jidar.shutdown();

API keys are server-side only. Never use this SDK in browser, frontend, or mobile code. Never expose keys in logs, screenshots, or repositories.

Do not send passwords, cookies, auth headers, tokens, raw request headers, or full request bodies. The SDK is a thin ingestion client only; detection, billing, tenant isolation, storage, and response logic stay server-side.

Python SDK

Package registry coming soon. Direct HTTP ingestion is supported today; private beta/source users should follow Jidar-provided instructions.

PHP SDK

Package registry coming soon. Direct HTTP ingestion is supported today; private beta/source users should follow Jidar-provided instructions.

Go SDK

Package registry coming soon. Direct HTTP ingestion is supported today; private beta/source users should follow Jidar-provided instructions.

Java SDK

Package registry coming soon. Direct HTTP ingestion is supported today; private beta/source users should follow Jidar-provided instructions.

.NET SDK

Package registry coming soon. Direct HTTP ingestion is supported today; private beta/source users should follow Jidar-provided instructions.

REST API — Events

Send events directly via HTTP POST. Direct HTTP remains supported for customers who do not want an SDK dependency. Expected success: 202 Accepted.

          POST https://api.jidar0x0.com/api/logs/batch

          Authorization: Bearer <server-side-api-key>

          Content-Type: application/json

          {

            "source_id": "backend-api",

            "sdk": { "name": "direct-http", "version": "1.0.0", "runtime": "node" },

            "events": [{

              "event_type": "auth.failed_login",

              "timestamp": "2026-05-10T00:00:00.000Z",

              "actor": { "email": "user@example.com" },

              "network": { "ip": "203.0.113.42", "user_agent": "Example" },

              "metadata": { "reason": "invalid_password" }

            }]

          }

          # Expected response: 202 Accepted

Webhooks

Subscribe to real-time threat notifications. Jidar will POST to your endpoint whenever a high-severity event is detected.

          # Webhook payload example (JSON)

          {

            "event": "threat.detected",

            "severity": "HIGH",

            "source_ip": "91.142.33.7",

            "description": "Brute-force SSH — 512 attempts/min",

            "timestamp": "2026-04-24T12:01:00Z"

          }