Governance API

Review workspace activity logs, approval requests, and rule settings for auditing, troubleshooting, and sync monitoring.

Last updated: July 14, 2026

Summary

Use Governance API when your integration needs to review what happened in a Sanka workspace or manage approval controls. It is separate from Object API because it reads operational evidence and governance state across multiple objects instead of creating or updating one record type.Governance API includes GET /v2/public/logs, /v2/public/approval-requests, and /v2/public/approval-rules.

What's included

How to use it

  1. Create a Developer API key with read access.
  2. Call GET /v2/public/logs when you need to inspect recent activity.
  3. Filter by workspace, actor, object, or time range when available.
  4. Store the returned log IDs with your integration job when you need an audit trail.
  5. Link log rows back to the source record or workflow run in your own monitoring UI.
Example request:
cURL
curl "https://api.sanka.com/v2/public/logs" \
  -H "Authorization: Bearer <api_key>"

Common patterns

GoalUse
Confirm that an integration write happenedActivity Logs
Investigate who changed a recordActivity Logs
Monitor workflow or API-side activityActivity Logs
Build a customer-facing audit viewActivity Logs with object IDs
Use Object API for the actual record operation, then use Governance API to confirm activity history or manage the related approval controls.

Next steps