Organizations get a full audit trail of significant actions, and you've been able to read it over the API for a while. Now your app can write to it as well — record an action it took in its own system so it lands in the same timeline as everything Examplary logs itself.
POST /audit-logs takes an action in resource.action form, the object it acted on, and optional session, reason and before/after snapshots. It needs the new audit-logs:write scope — not granted by default — and only OAuth apps can call it; JWT and API-key callers get a 403. Entries are attributed to the token's own actor and marked as coming from an app, so they're never mistaken for Examplary's own.