Audit Log
Your tenant keeps a security audit log: who signed in, who gave whom access, who changed sign-in, API keys, settings or webhooks, who exported or restored data, and, when you ask for it, what Quantaprice staff did on your tenant. Read it in the console (Settings → Audit log) or let your SIEM (Splunk, Microsoft Sentinel, Elastic, …) fetch it from the API.
Price, article and pricelist changes are not in the audit log; they are in the change log.
What is guaranteed
- Complete. A change that succeeds always produces its event. When the audit log cannot be written, the service that made the change keeps the event and delivers it later.
- Append-only. Nothing edits or deletes an event. Each event carries the hash of the event before it, so an edit or a gap is detectable (see Checking the chain).
- Outside your data. Restoring a backup, purging or deleting your tenant's data does not touch the audit log.
- Kept 30 days. A longer period is available on the Enterprise plan; ask Quantaprice.
- Bounded. Requests refused for a missing permission are counted per caller, operation and minute in one event; refused sign-ins per client address, reason and minute. Price queries and data writes produce no events.
Reading it from the API
GET https://YOUR_TENANT.quantaprice.com/api/audit/events?cursor=…&from=…&to=…&type=…&limit=…
Authorization: Bearer <token>
Use an API key that carries the audit:read scope (create one under Settings → API keys), or sign in as a person holding the audit:read permission (the Owner role holds it).
| Parameter | Meaning |
|---|---|
cursor | Resume after the last event you read: the next_cursor of your previous page. Leave it out to start from the oldest event kept. |
from, to | ISO 8601 times. Events at or after from and before to. |
type | Comma-separated event types or areas: signin.failed, or signin for every sign-in type. |
limit | Events per page, 1 to 1,000. Default 100. |
Events come oldest first. The answer:
{
"items": [ { "id": "…", "time": "…", "type": "signin.failed", "…": "…" } ],
"has_more": false,
"next_cursor": "c2VxOjQy",
"estimated_total": 42
}
A collector stores next_cursor after each page and asks with it next time; it always resumes exactly where it stopped, also when the last page was empty. The endpoint answers 60 requests a minute per tenant; past that it answers 429 with Retry-After.
Each event
| Field | Meaning |
|---|---|
id | Unique; use it to drop duplicates. |
time | When it happened, UTC. |
type | area.action, see below. |
ocsf_class | The OCSF class the type maps to. |
outcome | { "result": "success" | "failure", "reason": … } |
actor | { "kind": "person" | "api_key" | "staff" | "system", "id": email or API key id, "name": … } |
source | { "ip": client IP, "user_agent": … } where there was a request, else null. |
target | What was acted on: { "kind", "id", "name", "before", "after", "details" }. Never a secret, token or key secret. |
prev_hash, hash | The chain, see below. |
Event types
| Type | OCSF class | When |
|---|---|---|
signin.succeeded | Authentication (3002) | A person signed in; target.details.method: email_link, google, microsoft, tenant_idp, or sso when a person already signed in (to account-ui or another tenant) entered your console without signing in again, with the application they came from in target.details.from. |
signin.failed | Authentication (3002) | A sign-in failed; outcome.reason says why. target.details.method directory: the platform directory accepted the person but the sign-in service then refused the sign-in (target.details.refused_by). Refused sign-ins to the platform directory are one event per client address, reason and minute: target.details.count of them, the first emails tried in target.details.emails. |
signin.link_requested | Authentication (3002) | A sign-in email link was requested. |
signin.signed_out | Authentication (3002) | A person signed out. |
session.ended | Authentication (3002) | A session ended; target.details.reason: lifetime, revoked, or renewal_refused when your own IdP refused to renew it. |
session.refresh_token_reused | Authentication (3002) | A used refresh token was presented again; the session was ended. |
consent.granted, consent.denied | User Access Management (3005) | A person allowed or refused a third-party app (MCP client). |
apikey.created, apikey.revoked, apikey.deleted | Account Change (3001) | An API key, with its scopes. |
apikey.token_issued | Authentication (3002) | A token was issued for an API key. |
apikey.secret_invalid | Authentication (3002) | A wrong secret was presented for an API key. |
user.created, user.deleted | Account Change (3001) | A directory user was created or deleted. One made or removed by a platform service (actor.kind system) has target.details.via: directory_api, or access_sync when giving or taking away a person's access did it. |
invite.created, invite.revoked, invite.accepted | Account Change (3001) | An invitation. |
person.removed | User Access Management (3005) | A person was removed from the tenant. |
role.assigned, role.removed | User Access Management (3005) | A person's role, before and after. |
role.created, role.changed, role.deleted | User Access Management (3005) | A tenant-defined role. |
permission.granted, permission.revoked | User Access Management (3005) | A permission given to or taken from a person by name. |
tenant.signin_settings_changed | API Activity (6003) | How people sign in, before and after. |
tenant.terms_accepted | API Activity (6003) | A member accepted the terms of service. |
tenant.deletion_requested | API Activity (6003) | Someone asked to delete the tenant. |
staff.plan_changed, staff.limits_changed, staff.settings_changed | API Activity (6003) | Quantaprice changed your plan, limits or platform settings. |
staff.deletion_scheduled | API Activity (6003) | Quantaprice scheduled (or cancelled) the tenant's deletion. |
staff.status_changed | API Activity (6003) | Quantaprice blocked, unblocked or revived the tenant: the status and scheduled deletion before and after. |
staff.tenant_deleted | API Activity (6003) | Quantaprice deleted the tenant at once. |
setting.changed | API Activity (6003) | A tenant setting, before and after. |
webhook.created, webhook.changed, webhook.deleted, webhook.tested | API Activity (6003) | A webhook, with its target URL; a change or deactivation with its address, filter and active state before and after. |
backup.created, backup.downloaded, backup.restored | API Activity (6003) | A backup made, downloaded or restored by someone. |
data.purged | API Activity (6003) | All data was purged. |
request.refused | API Activity (6003) | Requests refused for a missing permission: one event per caller, operation and minute, target.details.count of them. |
Staff events (actor.kind staff) are recorded only when you ask Quantaprice to switch them on, from then on.
Checking the chain
hash is the SHA-256 (hex) of the previous event's hash, a newline, and the event without its hash field as JSON with keys sorted at every depth and no whitespace. The first event of a tenant has a prev_hash of 64 zeros. Each event's prev_hash equals the hash of the event before it. An edited event no longer matches its hash; a missing event breaks the next one's prev_hash. Events older than the retention period are removed from the start of the chain; the oldest kept event's prev_hash names the one removed before it.