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

Azure Log Analytics Ingestion API

Send log data to Log Analytics workspaces

Azure Log Analytics Ingestion API is one of 5 APIs that Azure Log Analytics publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 5 JSON Schema definitions.

Tagged areas include Ingestion. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, a getting-started guide, a JSON-LD context, and 5 JSON Schemas.

This API exposes 1 operation across 1 path, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2023-01-01.

Requests are made against a single base URL, https://{endpoint}.

1 operations 1 paths 4 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2023-01-01
Base URL
https://api.loganalytics.azure.com/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Azure Log Analytics Ingestion API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Microsoft Entra ID OAuth2 Bearer token obtained via client credentials flow. Use scope https://monitor.azure.com/.default for Azure public cloud.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Ingestion 1

Send log data to Log Analytics workspaces

POST
/dataCollectionRules/{dcrImmutableId}/streams/{streamName}
Azure Log Analytics Upload Logs
uploadLogs 5 params body → 204400401403404413429500

Schemas 4

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

ErrorDetail
object
Detailed error information.
2 properties
LogEntryArray
array
Array of log entry objects. Each object must match the stream schema defined in the data collection rule.
LogEntry
object
A single log entry. The schema must match the stream declaration in the data collection rule. Custom columns must have the CF suffix for Azure tables.
3 properties
ErrorResponse
object
Error response from the ingestion API.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

azure-log-analytics-ingestion-api-openapi.yml Raw ↑

Other APIs Azure Log Analytics publishes across the network.

Azure Log Analytics Query API
Azure Log Analytics Saved Searches API
Azure Log Analytics Tables API
Azure Log Analytics Workspaces API
Where this information came from

This is an independent, third-party profile of Azure Log Analytics Ingestion 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.