BizKitHubDocs

/api/v1/tracking/log

Sentry-like logging endpoint for centralized log ingestion.

Accepts log events from frontends (React/Next.js), backend services, workers and third-party systems. Each request creates a single log entry bound to the organisation, classified by severity and optionally eligible for notifications.

Debouncing can be enabled to group repeated/noisy events. useDebounce supports a simple boolean or an advanced configuration with a custom key and a relative time window (maxInterval, e.g. 10m, 1h 30m, or minutes).

post
Tags:tracking
Operation ID: postApiV1TrackingLog
Query Parameters
Body
messagestring
required

Log message payload. Intended for system/application logs coming from external services/websites. Keep it human-readable or JSON; include essential context (e.g., module, action, identifiers) to make triage easier. For structured data, serialize into the message or extend the endpoint to accept extra fields.

Example: "[checkout] Payment callback failed: missing transId (orderId=25000233)"
levelstring
optional

Severity level of the log entry. Used for filtering, alerting and retention rules.

  • info = diagnostic signal
  • success = positive milestone
  • warning = potential issue
  • error = failure that impacted a request/job
  • critical = high priority incident requiring immediate attention.

If omitted, the backend should treat it as a default level (commonly info).

Example: "error"
sendNotificationboolean
optional

When true, the log entry is eligible to trigger notifications (e.g., email/Slack/push) according to organisation settings. Use sparingly for actionable events (typically error/critical). If omitted, the system decides based on level and notification rules.

Example: true
useDebouncestring
optional
Responses
200

No description

Base URL:
https://bizkithub.com

Example Request

fetch('https://bizkithub.com/api/v1/tracking/log?apiKey=YOUR_API_KEY', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
        "message": "[checkout] Payment callback failed: missing transId (orderId=25000233)",
        "level": "error",
        "sendNotification": true
    })
})

Example Response

HTTP 200Success Response
{
  "success": false
}

🔑 API Key Required

All BizKitHub API endpoints require authentication using an API key. The API key must be passed as a GET parameter in the URL for all requests.

Get API Key →API Overview →
Back to API Documentation
Last updated: January 2, 2026