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

Okta Log API

The Log API from Okta — 1 operation(s) for log.

Okta Log API is one of 28 APIs that Okta publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 4 JSON Schema definitions.

Tagged areas include Log. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, authentication docs, rate-limit docs, a JSON-LD context, and 4 JSON Schemas.

This API exposes 1 operation across 1 path, and defines 19 schemas. It is described by OpenAPI 3.0.1, at version 2.16.0.

Requests are made against a single base URL, https://your-subdomain.okta.com/.

1 operations 1 paths 19 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
2.16.0
Base URL
https://your-subdomain.okta.com
Authentication
API Key
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Okta Log API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (api_token).

  • api_token — SSWS {API Token}

Paths & Operations 1

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

Log 1
GET
/api/v1/logs
Fetch a list of events from your Okta organization system log.
getLogs 7 params → 200

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are LogEvent (16 properties), LogAuthenticationContext (7 properties), LogClient (6 properties), LogTarget (5 properties). Each schema is shown below with its type and property counts.

LogRequest
object
1 property
LogSecurityContext
object
5 properties
LogCredentialProvider
string
LogSeverity
string
LogTarget
object
5 properties
LogTransaction
object
3 properties
LogAuthenticationContext
object
7 properties
LogGeographicalContext
object
5 properties
LogGeolocation
object
2 properties
LogUserAgent
object
3 properties
LogActor
object
5 properties
LogAuthenticationProvider
string
LogOutcome
object
2 properties
LogEvent
object
16 properties
LogIpAddress
object
4 properties
LogClient
object
6 properties
LogDebugContext
object
1 property
LogIssuer
object
2 properties
LogCredentialType
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

okta-log-api-openapi.yml Raw ↑

Other APIs Okta publishes across the network.

Cross-App Access (XAA)
Okta for AI Agents
Okta Application API
Okta Authenticator API
Okta AuthorizationServer API
Okta Brand API
Okta Domain API
Okta EventHook API
Okta Feature API
Okta Group API
Okta GroupSchema API
Okta IdentityProvider API
Where this information came from

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