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 byoperationId. 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).
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.