Audit Logs

Unqork logs administrative and configuration activity across the platform. Audit logs capture who performed an action, what changed, and whether it succeeded. Each entry provides a traceable record for compliance, troubleshooting, and security review.

Audit logs are not available through the UnqorkAI platform. Access is through the API Reference using the GET /logs/audit-logs endpoint. Designer Administrator access is required. Events are uploaded in batches, so a new entry is not available immediately. See Update Frequency for the timing by hosting platform.

Event Structure

Each audit log entry includes the following fields. The eventAction values listed in this article are the values of the action field.

Many modification events also record the prior state of the resource in object.priorAttributes for before-and-after comparison. Modification events that change no values are not logged.

Audit log entries contain personal information, including the email address, name, and phone number of the Creator or end-user in actor.attributes. Store, transmit, and process exported logs according to the organization's data protection and encryption standards.

Logged Events

The following tables list each tracked eventAction value by category. For the full attribute schemas returned with each event, see the attribute reference articles linked in See Also.

Applications

Client Tracker Administration

Creator Roles

Creator Users

Email Templates

Environment Administration

Excel Fill Template Administration

Express Groups

Express Roles

Express Users

Global Variables

Managed Assets

Modules

Module Submissions

Queries

PDF Template Administration

Single Sign-On (SSO)

Smart Components

Smart Component audit events require UnqorkAI (9.0.0 and later).

Start Node Administration

Style Administration

Themes

Theme audit events require UnqorkAI (9.0.0 and later).

LLM Credentials and Service Administration

LLM Credential audit events require UnqorkAI (9.0.0 and later).

The service-administration event action covers all service-level configurations, including LLM Credentials, Integration Gateway services, and others. Filter by the serviceProtocol or authType fields in object.attributes to isolate events for a specific service type.

Integration Gateway

Workflow Submissions

Workspaces

Application Versioning

Application Versioning audit events require the Branch & Merge Beta.

Bring Your Own Component (BYO)

Comments

Search Configuration

Workflow Access

Querying Audit Logs

Endpoint: GET /logs/audit-logs

Access: Designer Administrator only.

Update Frequency

Unqork uploads audit log events in batches instead of writing each event as it occurs. A new event is not available to query until its batch uploads. A batch uploads when the upload interval elapses or the batch reaches its size limit, whichever comes first.

The following table lists the approximate upload interval and batch size limit by hosting platform.

A query window that ends in the most recent upload interval can return incomplete results. Rerunning the query after the interval elapses returns the missing events.

Query Parameters

The query window must not exceed one hour, and start time must be before end time.

Example request:

GET /logs/audit-logs?startDatetime=2026-04-13T10:00:00.000Z&endDatetime=2026-04-13T11:00:00.000Z

Both startDatetime and endDatetime must be set to the exact minute. Seconds and milliseconds must be 0. The window in this example is exactly one hour, which is the maximum allowed.

Response

{
  "logLocations": ["string"]
}

The response returns an array of download links for the log files in the requested time window. Each link expires 15 minutes after the response is returned. Log files are stored in gzip (.gz) format. Set unzip to true to receive decompressed content.