Skip to content

Audit Logs

Advanced event logging, auditing, and exporting for IT admins

Enterprise-grade compliance with a customizable, strongly-typed, exportable audit logging solution.

Add Audit Logs to your appRead the docs
Audit Logs
Available on every plan
Enabled for your workspace
Configured by your customer
3Streaming to your systems

How it works

A world-class audit log in minutes

1

Define events

Use the Paycux dashboard to define the actions, targets and metadata that you want to record from your app.

2

Send event data

With a few lines of code, use our SDK to send actions, targets and metadata from your app to the Audit Log API.

3

View and export logs

Audit Logs are available to you in the Paycux dashboard and to your customers through a private URL.

Define events

Decide what is worth recording, once

A developer-friendly interface lets you quickly add the events you want to track, name the action, assign target types, and define a schema for any custom metadata you attach to each event.

  • Name an action and assign the target types it applies to
  • Describe custom metadata with a JSON schema editor
  • Enforce strongly-typed metadata so malformed events are rejected, not stored
  • Version an event definition as your product changes shape
Define events
Available on every plan
Enabled for your workspace
Configured by your customer
3Streaming to your systems

Log streaming

Stream audit logs to your customer's existing SIEM provider

Give your customers enhanced log management with streaming logs. The best part: they can set it up themselves with their existing SIEM provider, directly from the Paycux Admin Portal.

  • The customer's security team configures the destination themselves
  • Events arrive in their SIEM in the shape their analysts already query
  • No engineering ticket on your side when they switch vendors
  • Search, filter and CSV export stay available in the dashboard alongside it
Log streaming
Available on every plan
Enabled for your workspace
Configured by your customer
3Streaming to your systems

Create events and attach custom metadata

The audit trail their security team asks for

Create audit log events at any point in your application lifecycle, attach your own metadata, and optionally validate against a JSON schema.

Attach events to different actor typesChoose between user, anonymous and system actor types to fit your use case.
Assign targets to each eventSpecify which object types in your application a given event is associated with.
Add custom metadataCustom metadata can be added to the top-level event, the actor, or any of the targets associated with it.
Type-check with JSON schema validationEnsure any event data sent by your app is structured and typed correctly.
View and export logsA quick, robust filtering engine makes searching, viewing and exporting audit log data a breeze, including CSV export.
Append-only by designEvents are written once and never edited, which is exactly the property an auditor is looking for.

Send events

Emit an event from anywhere in your app

SDKs for Node.js, Ruby, Python, PHP, Go and more, plus an idempotent HTTP endpoint so a retry never doubles an entry.

1// Emit an Audit Log event
2// using the ID from an Organization
3import Paycux from '@paycux/node';
4 
5const paycux = new Paycux('sk_example_123456');
6 
7await paycux.auditLogs.createEvent('org_01EHWNCE74X7JSDV0X3SZ3KJNY', {
8  action: 'user.signed_in',
9  occurred_at: new Date(),
10  actor: {
11    type: 'user',
12    id: 'user_01GBNJC3MX9ZZJW1FSTF4C5938',
13  },
14  targets: [
15    {
16      type: 'team',
17      id: 'team_01GBNJD4MKHVKJGEWK42JNMBGS',
18    },
19  ],
20  context: {
21    location: '123.123.123.123',
22    user_agent: 'Chrome/104.0.0.0',
23  },
24});

Transparent pricing

Priced by SIEM connection and retention tier

Give your enterprise customers advanced event logging, auditing, storage and streaming to SIEM providers. Streaming is billed per connection; storage is billed by how long events are kept and how many there are.

See full pricingTalk to an expert
Log streaming, per SIEM connectionContact us
Event retention tierVolume pricing
Dashboard search and filteringIncluded
CSV exportIncluded
Custom enterprise planContract-based

Questions

Frequently asked

What counts as an audit log event?

Anything your customer's security team would want to see later: a sign-in, a permission change, a record deleted, a billing plan upgraded. You define the actions, the target types they apply to, and the metadata each one carries.

Can my customers see their own logs?

Yes. They get a private URL scoped to their organization, where they can filter by actor, event, target and date, and export what they find as CSV without asking you for a dump.

How does SIEM streaming work?

Your customer configures a destination themselves from the Admin Portal, and events for their organization stream there as they are written. You are not in the loop when they change vendors.

What stops us sending malformed events?

The JSON schema you attach to an event definition. Metadata that does not match is rejected at the API boundary, so a mistyped field is a failed call in staging rather than a hole in the audit trail a year later.

Can an event be edited or deleted afterwards?

No. The log is append-only. Correcting the record means writing a new event that says so, which is what an auditor expects to find.

Keep exploring

The rest of the platform

User ManagementComplete auth and user management platform
Enterprise SSOUnified SSO for any identity provider
RadarRealtime protection against bots, fraud and abuse
AuthKitCustomisable UI for every authentication type
Directory SyncUser lifecycle from corporate directories
Role-Based Access ControlPowerful and flexible permissions for your users

Pass the security review, not the deadline

Define your events this afternoon and hand your customer's security team a filterable, exportable, streamable trail before they ask for one.

Get startedTalk to an expert