Telemetry is never writable
The public API cannot be talked into accepting connection records.
PUBLIC API
A public read API with tenant scope built in.
Use tenant-scoped credentials, cursor pagination, stable error codes, and supported SDKs for TypeScript, Python, and Go.
Context
The situation
If the data is yours, you should be able to get it without a screenshot. A read API on a privacy product is also the surface most likely to become a leak, so its shape matters more than its feature list.
A versioned read API, authenticated with tenant-scoped credentials. Cursor pagination. Generated SDKs for TypeScript, Python, and Go, published from the OpenAPI description. The interactive console lives on the developer portal.
On this page
What you get from this
Quotas are published
When a quota is hit, a documented error code returns with a retry hint, not a silent truncation.
Personal has no API
The read API starts on Pro.
Collection boundary
The boundary
We observe here
Aggregates, conformity results, posture results, alerts, audit records, configuration objects, and device inventory, all scoped to the calling principal's tenant, derived server-side.
We never collect here
A telemetry write. Write scope is limited to configuration objects. There is no endpoint, parameter, header, or scope that makes telemetry writable. A tenant identifier supplied by a caller is ignored — scope comes from the authenticated principal, never from input.
Coverage is not complete. Some traffic paths are not observable from the interfaces we use, and geolocation is advisory rather than authoritative.
Availability across plans
Personal
Not included
Pro
Read-only
Team
Read-only, higher quota
Enterprise
Read plus configuration write