Show which user triggered an action via API instead of displaying "unknown"
released
Taylor Jennings
When an action is triggered via API, the initiating user shows as "unknown" in the logs. Admins trying to audit API activity have no visibility into who or what system made the call.
When an action is triggered via the API, Chili Piper should display the user or service account associated with the API key used, so the initiating party is visible in logs and audit trails.
"Unknown" as an actor in logs makes auditing meaningless and slows down troubleshooting. Identifying the API caller improves accountability and makes it possible to trace activity back to its source.
Taylor Jennings
marked this post as
released
Admins can see who's calling using MCP/Edge API
The Request Logs view (Integrations → API & Credentials → Logs) now shows a Caller column – the user for MCP or API token name via Edge, alongside method, path, status, duration and auth method. Gives admins an audit trail of their own API and MCP usage.