Skip to main content
Audit Logs provide a comprehensive, searchable record of all API activity within your organization. Every request made to the Didit platform — whether from the Console, your integration, or team members — is automatically logged for security, compliance, and troubleshooting.
Audit logs in the Didit console

Why audit logs?


Accessing audit logs

Open Settings > Organization > Audit log in the Didit Console. The interface displays a chronological list of all API requests made within your organization. Each log entry includes:

Decisions taken by the Investigator

Each decision the Investigator takes on its own is recorded under The Investigator, not under a member or an API key: approving or declining a session or requesting a resubmission, setting a transaction’s status, and resolving a case, escalating it or requesting information on it. The entry links to the Investigator report behind the decision. When a person accepts or overrides an Investigator recommendation, the entry is recorded under that person.
The Audit Logs interface provides powerful filtering capabilities to help you find exactly what you’re looking for. The search bar automatically detects what you’re looking for:

Available filters


Data retention

Your plan sets how far back you can read the audit log and whether you can export it: An export on a plan without it answers 403 with "code": "plan_limit_exceeded".

Security and privacy

What’s logged

Audit logs capture metadata about API requests:
  • Request timestamp and duration
  • User identity (email, user ID), or the API key that made the request (its name and the first characters of its secret, never the full secret)
  • Request path and query parameters
  • Response status codes
  • Client IP address and user agent

Request and response bodies of API key calls

For a call made with an API key, the audit log also keeps a redacted copy of the JSON request body of a write and of the response to a write or to an error, so you can see why a call failed. The response to a successful read is not kept. The redaction is default-deny:
  • The structure stays: field names, nesting, value types, array lengths and string lengths.
  • A value stays only when it is one of Didit’s own identifiers, statuses, codes, counts or timestamps, in a field Didit defines, with the shape that field expects.
  • A boolean stays only in a field Didit defines.
  • Every other value is replaced by a marker naming its type and length, such as [redacted:string:12], [redacted:number:5] or [redacted:boolean], and null stays null.
  • A field name that is not a plain identifier, such as an email address or a phone number used as a key, is replaced by [redacted:key:23].
  • A body that is not JSON, such as a form or a file upload, is replaced by a note saying what it was.
  • What remains is cut at 4,096 characters.
Query parameters go through the same redaction. Only standard headers such as content-type, user-agent and the rate-limit headers are kept; every other header is dropped with its value. A value your own system sends, for example in metadata or vendor_data, is never kept, even when its field is named like one of Didit’s.

What’s NOT logged

To protect sensitive data, the following are automatically excluded:
  • Authentication tokens and credentials
  • Passwords and secrets
  • Personal data from verification sessions

Access control

Viewing the audit log needs the audit-logs read and list permissions. The Reader, Compliance Officer, Developer, Admin and Owner roles all have them, and a custom role gets them by selecting Audit logs in the role editor.

Common use cases

Demonstrate to auditors that you have complete visibility into who accessed verification data:
  1. Filter by date range matching the audit period
  2. Filter by specific applications or users if needed
  3. Export or screenshot the results for documentation
If you suspect unauthorized access:
  1. Search for the affected user’s email or suspicious IP addresses
  2. Filter by date range around the suspected incident
  3. Look for unusual patterns: failed authentication attempts, unexpected endpoints, odd hours
When troubleshooting API integration issues:
  1. Search for the specific endpoint path
  2. Filter by 4xx or 5xx status codes to find errors
  3. Note the timestamps to correlate with your application logs
Monitor how your team uses the platform:
  1. Filter by specific team member emails
  2. Review which sessions and features they accessed
  3. Ensure team members are following proper procedures

Best practices

  1. Regular reviews — periodically review audit logs to catch anomalies early.
  2. Narrow your search — use specific filters to reduce noise and find relevant entries faster.
  3. Date ranges — always specify a date range for better performance on large datasets.
  4. Bookmark searches — save common filter combinations as browser bookmarks for quick access.
Last modified on October 31, 2026