Export audit logs to a SIEM
Your security team can pull Sessionboard’s logs into its SIEM — Splunk, Microsoft Sentinel, Elastic or any tool that can call a REST API on a schedule. The SIEM uses a dedicated log export token that reads logs and nothing else.
Why use it
Section titled “Why use it”If your security team watches activity across your organization’s tools in a SIEM, this export puts Sessionboard’s sign-ins, API requests and data changes there too. The log export token reads logs and nothing else, so you can hand it to the security team without giving them access to your event data. Reach for it when a security review or an audit asks who signed in from where, or who changed a record and when.
What you can export
Section titled “What you can export”| Log | What it holds | Kept for |
|---|---|---|
| API requests | Every request made with your organization’s API tokens to the Public API, the MCP server and Insights, with the caller, IP address, result and response time. Requests refused at sign-in are included with the reason when Sessionboard can tell which organization they belong to — a revoked key, an expired token, an archived organization, or a key whose owner is no longer an active member. A missing key or a key Sessionboard does not recognize belongs to no organization, so those attempts are not in your export. | 365 days |
| Security events | Sign-ins, failed sign-ins, two-factor and passkey events, passwords set or changed (password.set, password.changed), password resets and sign-outs by the people in your organization. | No limit |
| Audit trail | Every recorded change to your data: who changed which record, which field, and the new value. | No limit |
Every log arrives in the same event format, so your SIEM needs one field mapping for all three.
Create a log export token
Section titled “Create a log export token”You need permission to manage users in your organization to create or change a log export token. Without it, Audit log export shows greyed out in Create Token, with the reason.
Open API Tokens
Go to Organization Settings > API Tokens and click Create Token.
Name the token
Give it a name your security team will recognize, for example Splunk log export.
Check Audit log export
Under Permissions, check Audit log export (read:audit_logs). The other permissions and the event restriction disappear: a log export token holds only this permission and always covers your whole organization.
Copy the token
Click Create Token and copy the token straight away — it is shown only once. Hand it to your security team through your password manager or secrets vault.
In the token list, the token shows an Audit log export badge.
What a log export token can’t do
Section titled “What a log export token can’t do”- It can’t read or change events, sessions, contacts or any other data. Every other endpoint refuses it.
- It can’t be limited to particular events.
- It can’t be combined with other permissions. Create a separate token for any other integration.
- It can’t be used through an AI assistant connection.
Connect your SIEM
Section titled “Connect your SIEM”Your SIEM calls one address per log and keeps a bookmark, so each pull picks up exactly where the last one ended — nothing is missed and nothing is sent twice. New events show up about a minute after they happen.
Use the host for your region:
- US:
https://public-api.sessionboard.com - EU:
https://public-api-eu.sessionboard.com
Setup steps for Splunk, Sentinel and Elastic, with a ready-to-use Splunk script, are in Exporting logs to a SIEM in the API documentation.
