How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Weidmüller Logging API

Centralized system logging, capture and reporting API for u-OS

Weidmüller Logging API is one of 16 APIs that Weidmüller publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 5 JSON Schema definitions.

Tagged areas include Logging. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 5 JSON Schemas.

This API exposes 4 operations across 4 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.5.0-next.

Requests are made against a single base URL, /u-os-adm/api/v1.

4 operations 4 paths 6 schemas 3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.5.0-next
Server
/u-os-adm/api/v1
Authentication
OAuth 2.0
Contact
Weidmüller
License
MIT
Resource Areas
1

Authentication & Security 1

Weidmüller Logging API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow, exposing 20 scopes.

  • OAuth2 — The HTTP API uses the OAuth2 client credentials flow.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 3 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Logging 4

Centralized system logging, capture and reporting API for u-OS

GET
/logging/entries
Get all log entries
get_logging_entries 4 params → 200default
POST
/logging/reports
Trigger the generation of a report
create_logging_report → 202409default
GET
/logging/reports/{report_id}
Get the report by the given reportid
get_logging_report 1 param → 200default
GET
/logging/sources
Get available log sources
get_logging_sources → 200default

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are HttpErrorPayload (5 properties), LogEntry (3 properties), LogEntryResponse (2 properties), CreateLogReportResponse (1 property). Each schema is shown below with its type and property counts.

LogEntryResponse
object
2 properties 1 required
LogEntry
object
3 properties 3 required
LogSource
object
1 property 1 required
HttpErrorPayload
object
Common error payload structure for HTTP responses. Based on [RFC 9457](https://datatracker.ietf.org/doc/html/rfc9457)
5 properties 3 required
LogSourcesResponse
object
1 property 1 required
CreateLogReportResponse
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

weidmueller-logging-api-openapi.yml Raw ↑

Other APIs Weidmüller publishes across the network.

Weidmüller u-OS Data Hub Variable-NATS API
Weidmüller Consumer API
Weidmüller Firewall API
Weidmüller Network API
Weidmüller Operations API
Weidmüller Ping API
Weidmüller Realtime API
Weidmüller Recovery API
Weidmüller Security API
Weidmüller Serial Interfaces API
Weidmüller Syslog API
Weidmüller System API
Where this information came from

This is an independent, third-party profile of Weidmüller Logging API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.