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

Unify Logs API

Structured logging — create, query, derive, and manage log entries

Unify Logs API is one of 8 APIs that Unify publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

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

This API exposes 14 operations across 9 paths, and defines 1 schema. It is described by OpenAPI 3.0.3, at version 0.

Requests are made against a single base URL, https://api.unify.ai/v0.

14 operations 9 paths 1 schemas 2 DELETE4 GET2 PATCH5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
0
Base URL
https://api.unify.ai/v0
Authentication
HTTP Bearer
Contact
License
Resource Areas
1

Authentication & Security 1

Unify Logs API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — API key from the Unify console (UNIFYKEY environment variable)

Paths & Operations 14

Across 9 paths, the API surfaces 14 operations — 2 DELETE, 4 GET, 2 PATCH, 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Logs 14

Structured logging — create, query, derive, and manage log entries

GET
/logs
Get logs
getLogs 4 params → 200
POST
/logs
Create log entry
createLog body → 200
PUT
/logs
Update log entries
updateLogs body → 200
DELETE
/logs
Delete log entries
deleteLogs body → 200
GET
/logs/fields
List log fields
getLogFields 2 params → 200
POST
/logs/fields
Query log fields
queryLogFields body → 200
DELETE
/logs/fields
Delete log fields
deleteLogFields body → 200
PATCH
/logs/fields/rename_field
Rename a log field
renameLogField body → 200
GET
/logs/metric/{metric}
Get log metric
getLogMetric 3 params → 200
GET
/logs/groups
Get log groups
getLogGroups 2 params → 200
POST
/logs/derived
Compute derived log fields
computeDerivedLogs body → 200
POST
/logs/join
Join logs
joinLogs body → 200
POST
/logs/join_query
Join query logs
joinQueryLogs body → 200
PATCH
/logs/{log_id}/fields/{key}/atomic
Atomic field update
atomicUpdateLogField 2 params body → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Log (5 properties). Each schema is shown below with its type and property counts.

Log
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

unify-ai-logs-api-openapi.yml Raw ↑

Other APIs Unify publishes across the network.

Unify Agent API
Unify Assistants API
Unify Contexts API
Unify Organizations API
Unify Platform API
Unify Projects API
Unify Spaces API
Where this information came from

This is an independent, third-party profile of Unify Logs 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.