Skip to content
Connect an agent

Organisations

Read who may read the audit log and the call history

The roles and people the owner let read the audit log and the call history, besides the owner and admins.

GET/orgs/{org}/log-access

TL;DR

QuestionAnswer
What does it do?Read who may read the audit log and the call history.
What does it take?org in the path.
What does it return?Status 200 with a body of type LogAccess.
What can go wrong?401 not signed in; 403 not the owner or an admin (orgs.forbidden); 404 no such organisation, or the caller is not a member of it; 429 too many requests; 503 organisations are not set up on this server. Every failure uses the one error envelope.

What it does

The roles and people the owner let read the audit log and the call history, besides the owner and admins. The owner and admins.

Path parameters

FieldTypeRequiredDescription
orgstringyesThe organisation's id or its slug.

Responses

StatusMeaningBody
200The setting.LogAccess
401Not signed in.ErrorResponse
403Not the owner or an admin (orgs.forbidden).ErrorResponse
404No such organisation, or the caller is not a member of it.ErrorResponse
429Too many requests.ErrorResponse
503Organisations are not set up on this server.ErrorResponse

Response body

A 200 answer has the type LogAccess.

FieldTypeRequiredDescription
roles("member" | "reader")[]yes
membersobject[]yes
members[].userIdstringyes
members[].emailstringyes
members[].role"owner" | "admin" | "member" | "reader"yes

See also

DocWhy
API referenceEvery endpoint, and the error envelope
SchemasEvery request and response type
Tool referenceThe operations as callable tools