Operator access to the account’s data
GET/audit/operator-access
When the Joinotify team opened your account's data — conversations, messages, contacts, campaigns, flows, events, billing —, newest first. It shows where and when, not who: the email and IP of whoever accessed it stay with the operation. The records are kept for 24 months.
An API key limited to some numbers gets 403: the trail belongs to the whole account.
Request
Responses
- 200
- 401
- 403
- 422
- 429
Paginated list.
Missing, malformed, unknown or revoked token (authentication), or a suspended
account (tenant_inactive).
The resource does not belong to your account (forbidden), or the path is on the
mirror's block list (forbidden_endpoint), or your API key is limited to some numbers and
the operation covers the whole account (forbidden).
Payload failed validation (invalid_request, detailed in issues) or was
rejected by Meta (meta_error, with the original body in meta).
Rate limit exceeded (rate_limit).
Response Headers
Seconds to wait before retrying.
Which rate limit category applied — send, media or default.
Which bucket the other headers describe — key (the API key), session (the dashboard) or account (the account ceiling).
Request ceiling for this category in the current window.
Requests left in the current window.