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

Nexla Audit Logs API

Operations for reviewing the change history of resources.

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

Tagged areas include Audit Logs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 12 operations across 12 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://{nexla-api-host}.

12 operations 12 paths 3 schemas 12 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://dataops.nexla.io/nexla-api
Authentication
HTTP Bearer, API Key, HTTP Basic, HTTP Basic, HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 5

Nexla Audit Logs API declares 5 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (NexlaSessionToken). An API key is passed in the query as api_key (NexlaApiKeyQuery). It accepts HTTP basic authentication (NexlaApiKeyHeader). It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (JWT) (GoogleSSOToken). By default, every request must be authenticated.

  • NexlaSessionToken — The first step in calling the Nexla API or Nexla CLI is to fetch a Session access token by logging on to your Nexla UI instance. This ensures that your authent…
  • NexlaApiKeyQuery — Important: Never share your API keys. Keep them guarded and secure. If you think the key has been compromised, you can rotate the API key by calling relevant A…
  • NexlaApiKeyHeader — Important: Never share your API keys. Keep them guarded and secure. If you think the key has been compromised, you can rotate the API key by calling relevant A…
  • GoogleSSOToken — The token that is used when logging into Nexla via Google SSO.

Paths & Operations 12

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

Audit Logs 12

Operations for reviewing the change history of resources.

GET
/data_sources/{source_id}/audit_log
Get Audit Log for a Data Source
get_data_source_audit_log 4 params → 200401403404
GET
/data_sinks/{sink_id}/audit_log
Get Audit Log for a Data Sink
get_data_sink_audit_log 2 params → 200401403404
GET
/data_sets/{set_id}/audit_log
Get Audit Log for a Nexset
get_nexset_audit_log 2 params → 200401403404
GET
/data_credentials/{credential_id}/audit_log
Get Audit Log for a Data Credential
get_data_credential_audit_log 2 params → 200401403404
GET
/data_maps/{data_map_id}/audit_log
Get Audit Log for a Data Map
get_data_map_audit_log 2 params → 200401403404
GET
/data_schemas/{schema_id}/audit_log
Get Audit Log for a Data Schema
get_data_schema_audit_log 2 params → 200401403404
GET
/code_containers/{code_container_id}/audit_log
Get Audit Log for a Code Container
get_code_container_audit_log 4 params → 200401403404
GET
/projects/{project_id}/audit_log
Get Audit Log for a Project
get_project_audit_log 4 params → 200401403404
GET
/doc_containers/{doc_container_id}/audit_log
Get Audit Log for a Document
get_doc_container_audit_log 4 params → 200401403404
GET
/users/{user_id}/audit_log
Get Audit Log for a User
get_user_audit_log 4 params → 200401403404
GET
/orgs/{org_id}/audit_log
Get Audit Log for an Organization
get_org_audit_log 4 params → 200401403404
GET
/teams/{team_id}/audit_log
Get Audit Log for a Team
get_team_audit_log 4 params → 200401403404

Schemas 3

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

LogEntry
object
16 properties
AsyncResponse
object
This object represents the response of an asynchronous operation. The response can be a dictionary or an array of dictionaries. The format of the response depe…
7 properties
audit_log_response

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nexla-audit-logs-api-openapi.yml Raw ↑

Other APIs Nexla publishes across the network.

Nexla Access Control API
Nexla Approval Requests API
Nexla Async Tasks API
Nexla Bulk Evaluation API
Nexla Bulk Query API
Nexla Clear Dataset Cache API
Nexla Clear Token Cache API
Nexla Code API
Nexla Code Containers API
Nexla Credential Mappings API
Nexla Credentials API
Nexla Custom Runtimes API
Where this information came from

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