The auditLog.list endpoint returns audit entries and accepts filters documented here. This page is the source of truth for targetTypes, categories, and actor.type values.
Forward compatibility: New category or target.type values may appear in responses as we add auditing — treat unknown values as valid. Request filters (targetTypes, categories) must use values from this page; unrecognized filter values return 400.
Each category belongs to exactly one target type. The tables below are grouped by target type so you can see which categories apply to each.
Actor types
Returned on each entry as actor.type. Filter by actor using actorIds in the request (the actor's id when present, not the type string).
actor.type
Description
User
An action performed by a person signed in to Ashby. actor.id is their user id.
Automation
An action performed by an automation or integration. actor.id may be null or a non-user identifier.
Other
Any other actor kind e.g API key, actor.id may be null.
How filters combine
Parameters
Combination
actorIds, targetIds
AND with each other and with activity filters — an entry must match every supplied dimension.
targetTypes, categories
OR with each other — an entry matching either list is included. To narrow to one job's status changes, use targetIds plus categories, not targetTypes + categories alone.
Empty arrays ([])
Ignored — same as omitting the parameter.
actorIds, targetIds, targetTypes, categories
Each array may contain at most 100 ids or values; longer arrays are rejected with a 400.
Pagination: Pass nextCursor only together with the same startDate, endDate, and filters as the request that produced it.
Date range examples
All dates are ISO 8601 interpreted as UTC.
Request
Window
{} (no dates)
Last 24 hours ending now
endDate only
24 hours ending at endDate
startDate only
24 hours starting at startDate (ends at startDate + 24h, not until now)
Both startDate and endDate
Explicit span (max 18 months)
Example — entries from 1 June 00:00 UTC through 7 June 00:00 UTC: