Teambridg API Goes Public: Build Custom Integrations

Opening Up the Platform

Since our 2021 roadmap announcement, API access has been one of our most anticipated features. Today, the Teambridg REST API is officially public and available to all Pro and Enterprise customers.

We've been running a private beta since March with 40 companies, and the integrations they've built have exceeded our expectations. Custom executive dashboards, automated HR reports, BI tool connections, and project management integrations — all built on top of Teambridg's data.

The API provides read access to all Teambridg metrics: focus time, collaboration patterns, work-hour distribution, wellbeing indicators, and hybrid location insights. Write access is available for configuration endpoints (teams, alerts, integrations). All endpoints respect existing privacy settings — if data isn't visible in the UI, it's not available via API.

What You Can Build

Here are the most popular use cases from our beta period:

Executive Dashboards: Pull Teambridg data into tools like Tableau, Power BI, or Looker to create executive-level views of organizational productivity and wellbeing. Several beta customers built dashboards that combine Teambridg data with financial metrics, project delivery data, and employee satisfaction scores for a holistic organizational health view.

HRIS Integration: Connect Teambridg to BambooHR, Workday, or your HRIS of choice. Automatically sync team structures, enrich employee profiles with productivity insights, and correlate monitoring data with HR metrics like tenure and engagement scores.

Project Management Correlation: Pull focus time and collaboration data into Jira, Asana, or Linear to understand the relationship between work patterns and project delivery. One beta customer discovered that sprints where focus time dropped below 3 hours/day averaged 30% longer delivery times.

Technical Overview

The API follows REST conventions with JSON payloads. Authentication uses OAuth 2.0 with scoped tokens — you can create tokens that access only specific endpoints and teams. Rate limits are generous: 1,000 requests per minute for standard endpoints, 100 per minute for computation-heavy analytics endpoints.

Key endpoint groups:

/teams: Team membership, structure, and configuration. /metrics: Focus time, collaboration, meeting load, and work-hour data. Filterable by team, individual (with consent), date range, and location type. /wellbeing: Wellbeing indicators at team-aggregate level. /insights: Pre-computed insights and trend analysis. /alerts: Configure and manage alert rules. /integrations: Manage connected services and webhooks.

Full documentation is at docs.teambridg.com/api, including interactive examples, code samples in Python, JavaScript, and Ruby, and a Postman collection for quick testing.

Privacy Architecture in the API

We spent as much time on the API's privacy architecture as on its functionality. Every API request runs through the same permission model as the web interface:

Scoped tokens: Tokens can be scoped to specific teams, date ranges, and metric types. A token created for the "Engineering" team cannot access "Sales" data. Individual-level data requires consent: Individual employee data is only available via API if the employee has explicitly consented to API access in their Teambridg settings. Team-aggregate data doesn't require individual consent. Audit logging: Every API request is logged with the requesting application, endpoint, and data accessed. Audit logs are available to account administrators. Data minimization: Endpoints return only the data requested. Unlike some platforms that return full data dumps, our endpoints are designed for precise queries that minimize data exposure.

The API opens up exciting possibilities for teams that want Teambridg's insights integrated into their broader tech ecosystem. We can't wait to see what you build — and if you create something great, let us know. We'll feature the best integrations on our blog and at our upcoming user conference.