Download the org's audit log
Every entry between `since` and `until` (at most 366 days), oldest first: the org's own and every brand's, each with the brand it happened in (`brand`, its id and name, or null for the org's own), to keep a copy or for a security tool such as a SIEM. CSV, JSON or NDJSON, streamed. On every plan, as far back as the org's plan keeps entries (its `audit_retention_days` in `GET /v1/plans`: 7, 30 or 365 days, or for ever, then 366 days at a time). Needs `org.auditLog.export` across the org. Ten an hour for an org. Each export is recorded as `org.audit_log_exported`, with the window it covered.
/v1/orgs/{org}/audit-log/exportEvery entry between since and until (at most 366 days), oldest first: the org's own and every brand's, each with the brand it happened in (brand, its id and name, or null for the org's own), to keep a copy or for a security tool such as a SIEM. CSV, JSON or NDJSON, streamed. On every plan, as far back as the org's plan keeps entries (its audit_retention_days in GET /v1/plans: 7, 30 or 365 days, or for ever, then 366 days at a time). Needs org.auditLog.export across the org. Ten an hour for an org. Each export is recorded as org.audit_log_exported, with the window it covered.
Authorization
bearer An org API key (sk_live_…, sk_test_…), or an access token from the Synq issuer (the synq brand, on the accounts host) for this API.
In: header
Path Parameters
The org's id
^org_[0-9a-hjkmnp-tv-z]{26}$Query Parameters
From this time on, inclusive. Left out, or before the oldest entry the org's plan keeps: from that oldest entry (the plan's audit_retention_days back), or 366 days before until on a plan that keeps entries for ever.
date-timeUp to this time, exclusive: now when left out, or when later. At most 366 days after since.
date-timeOnly this brand's entries. Left out: the org's own and every brand's.
ndjson: one JSON object a line, an audit event with its brand. json: one JSON array of them. csv: a header row, then one row an entry, metadata as JSON in its cell.
"ndjson"Value in
- "ndjson"
- "json"
- "csv"
Response Body
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://api.synq.build/v1/orgs/org_01h455vb4pex5vsknk084sn02q/audit-log/export" \ -H "Authorization: Bearer $SYNQ_API_KEY"[ { "id": "aud_01h455vb4pex5vsknk084sn02q", "created_at": "2026-10-21T12:00:00.000Z", "action": "org.updated", "actor": { "type": "member", "id": "usr_01h455vb4pex5vsknk084sn02q" }, "act_client_id": "string", "approval_id": "string", "brand_id": "brd_01h455vb4pex5vsknk084sn02q", "resource": { "type": "org", "id": "org_01h455vb4pex5vsknk084sn02q" }, "metadata": {}, "ip": "string", "user_agent": "string", "org_id": "org_01h455vb4pex5vsknk084sn02q", "brand": { "id": "brd_01h455vb4pex5vsknk084sn02q", "name": "Acme" } }]Read how AI agents’ changes are approved in an org GET
Whether the org requires approval for every change its members' AI agents ask for (`require_approval`, off by default), and how the calling person's are made there (`your_approvals`). Some changes always ask, and take a sign-in from the last 5 minutes to approve: money and people (billing and plans, inviting or removing members, roles, API keys, deleting or moving a brand) and sign-in security (an app’s redirect and sign-out addresses and how it proves itself, custom sign-in, sending and verified domains, turning a sign-in protection off, such as the breached-password check or PKCE, turning a token gate off, deleting it or taking a place off it, and loosening account linking). So does a change that makes a secret only you should see (a web or machine app’s client secret, a webhook’s signing secret), which shows once, on its approval page. Needs `org.read`.
Read the org's audit log GET
Newest first, filtered by action, actor, resource, brand and time. Needs `org.auditLog.view`: a brand's entries (`brand_id`) show where the credential has it in that brand, and the org's own entries (no brand: its members, billing, settings) where it has it across the org, an org role's. Rows are kept as long as the org's plan says: 7, 30 or 365 days, or for ever.