Skip to main content

About

Operations for the people side of your organization: list teammates, manage team invitations, read team performance analytics, and manage the key owner’s own profile. All operations go through the developer API gateway — one endpoint, called by operationId. If you haven’t set up a key yet, start with the Developer API Overview.

Operations

Teammates and profile (READ + WRITE scopes)

Team invites (ADMIN scope)

Team analytics (ADMIN scope)

Reporting reads over the same nightly snapshots as the web app’s Analytics pages — each response carries the asOfDate it was computed. Both take an optional period: SEVEN_DAYS | FOURTEEN_DAYS | THIRTY_DAYS | YEAR_TO_DATE (default THIRTY_DAYS).
Rate-limitedAnalytics operations are rate-limited per key. Exceeding the limit returns 429 rate_limited with a Retry-After header. Pipeline-level analytics (outcomes and funnel) live in the Pipelines API.
Everything is your organizationTeam operations are inherently org-scoped: listTeammates and listTeamInvites return only your organization’s people and invites, and createTeamInvite creates under your org. revokeTeamInvite takes an invitation id, but a foreign one is rejected — the service requires you to be an ADMIN of that invitation’s own organization. Analytics run against your org only (the gateway injects the org id, so it can’t be forged). See Authorization.

Example

Pull the last 7 days of team activity for a dashboard:
Full variable schemas, response shapes, and worked examples for every operation are available from the discovery endpoint.