- 3 minutes to read

Log API

Unlock true end-to-end visibility for your business transactions with the Nodinite Log API. This powerful API enables you to log events and messages from any integration platform or custom solution, providing a unified, secure, and searchable archive for all your business-critical data.

What you'll find on this page:

✅ Effortless end-to-end logging across all platforms
✅ Log events and messages from any system using REST
✅ Secure, encrypted archiving in Nodinite Log Databases
✅ Self-service access to log data with role-based Log Views
✅ Built-in Swagger documentation for rapid integration

The Nodinite Log API empowers you to achieve seamless logging across your entire integration landscape. Nodinite Log Agents leverage the Log API, and you can too—whether you use out-of-the-box solutions or develop your own integrations. Send Log Events using REST from any platform, including node.js, .NET, Java, and other WS* compliant technologies. All data is securely stored and archived in encrypted Log Databases.

The Nodinite Log API is a web application hosted in IIS and is installed as part of the Core Services package. Review the Prerequisites for deployment details.

Empower your business users with self-service access to log data (Log Events) using role-based Log Views.

graph LR subgraph "Log Sink" roLogSink[fal:fa-bolt Integration Flow Application] end subgraph "Web Server" roLogAPI(fal:fa-cloud-arrow-down Log API) end subgraph "SQL Server" roSQL1(fal:fa-database Configuration Database) --- roSQL2(fal:fa-database Active Log Database) roLogSink -->|Log Event with payload and context| roLogAPI roLogAPI --> roSQL1 end

Illustration: The Log API receives log events from any integration flow or application, then stores them securely in Nodinite databases.

The Log API features a built-in help page to get you started quickly.
Log API Help Page
Here's an example of the Help page for the Nodinite Log API.

Swagger support

Creating custom logging solutions is easy with the built-in Swagger documentation.
Swagger Feature
Here's a Swagger example for a Nodinite Log Event.

Frequently asked questions

Find answers to common questions and troubleshooting tips in the Troubleshooting user guide for the Nodinite Log API.

Critical: Understanding Log Events and Message Types

When you log events through the Log API, the Message Type field (or OriginalMessageTypeName) is critical for downstream features:

  1. Log Events are created - Your application logs events via the Log API
  2. Message Types are determined - Nodinite evaluates the Message Type field or auto-extracts from payload
  3. Search Fields are extracted - Search Field Expressions (configured per Message Type) extract business data
  4. Features work - Log Views, Non-Events Monitoring, and BPM use this extracted data

Without proper Message Types, your events won't have searchable business data. They'll be stored, but you won't be able to search by Order Number, Customer ID, or correlate transactions in BPM.

Learn more: Log Event Processing, Message Types, Search Fields

Next Step

Log Agents
Logging Service
Log Databases
Message Types - Critical for Search Field extraction
Search Fields - Extracted using Message Types
Non-Events Monitoring - Analyzes Log View data
Business Process Modeling (BPM) - Tracks end-to-end processes