Integrations & API

Integrations, Webhooks & API

Connect TeamContext to GitHub, Slack, and Jira. Build custom integrations with the REST API, WebSockets, and webhooks.

GitHub Integration

Connect your GitHub organization to TeamContext for automatic commit tracking, deployment monitoring, and AI agent code scanning.

Setup

  • Go to Settings → Integrations in the dashboard
  • Click Connect GitHub — you'll be redirected to GitHub's OAuth flow
  • Authorize TeamContext to access your repositories
  • Back in TeamContext, click Manage Repos to select which repositories to link

Features

  • Commit Tracking — All commits from linked repos appear in the dashboard
  • Deployment Monitoring — Track deployments from GitHub Actions
  • Repo Analysis — AI agents scan your repo's file tree for architecture, security, and performance issues
  • Project Auto-Linking — Repos are automatically matched to TeamContext projects via git remote URL

Slack Integration

Connect Slack to receive TeamContext notifications in your team channels.

Setup

  • Go to Settings → Integrations and click Connect Slack
  • Authorize TeamContext in your Slack workspace
  • Select the channel where notifications should be posted

Notifications Sent

  • Conflict Alerts — When overlapping work is detected
  • Summary Digests — Daily and weekly team summaries
  • Agent Scan Results — When critical or high severity findings are detected
  • Member Notifications — New member joins, handoff updates

Jira Integration

Link Jira projects to TeamContext to track issue status alongside your coding context.

Setup

  • Go to Settings → Integrations and click Connect Jira
  • Authorize TeamContext with your Atlassian account
  • Select the Jira project to link to your TeamContext project

Features

  • Project Linking — Link Jira projects to TeamContext projects
  • Issue Tracking — View Jira issue status within TeamContext context

Webhooks

Receive real-time HTTP notifications when events occur in your TeamContext workspace.

Setup

Go to Settings → Webhooks and create a new webhook. Provide your endpoint URL and select which events to subscribe to.

Available Events

turn:new New coding turn captured decision:new Technical decision extracted summary:new AI summary generated conflict:detected File overlap detected session:start Coding session started session:end Coding session ended

Security

Every webhook delivery is signed with HMAC-SHA256. Verify the signature using the X-TeamContext-Signature header and your webhook secret. The event type is in the X-TeamContext-Event header.

Delivery & Retries

  • Failed deliveries retry 3 times with exponential backoff (1s, 2s, 4s)
  • View delivery history with status, payload, and response for each attempt
  • Test your endpoint with a test payload before going live
  • Regenerate your webhook secret at any time from Settings

REST API

The TeamContext API powers the dashboard, CLI, and MCP server. You can use it directly to build custom integrations.

Base URL
https://api.teamcontext.ai
Swagger Docs
https://api.teamcontext.ai/api/docs
Rate Limit
60 req/min (global)
Response Format
{ data, success, message }

Authentication

Two authentication methods are supported:

# Bearer Token (JWT) Authorization: Bearer <access_token> # API Key X-API-Key: <your_api_key>

JWT access tokens expire after 15 minutes. Use the refresh token endpoint to get a new one. API keys don't expire but can be revoked from Settings.

Pagination

All list endpoints use cursor-based pagination:

GET /turns/list?limit=20&cursor=2026-03-31T10:00:00Z|uuid

Endpoint Groups

The API has 150+ endpoints organized into 20 groups. Full details are available in the interactive Swagger documentation.

Auth — Login, register, OAuth, 2FA, password reset
/auth/*
Sessions — Start, end, list, active, detail
/sessions/*
Turns — Create, batch, list, search
/turns/*
Decisions — List with category, branch, project filters
/decisions/*
Summaries — List, latest, regenerate
/summaries/*
Handoffs — CRUD + status updates
/handoffs/*
Plans — Generate, approve, tasks, markdown export
/plans/*
Tasks & Sprints — CRUD, comments, links, sprint management
/tasks/* /sprints/*
Projects — CRUD, enrich, markdown context
/projects/*
Insights — Conflicts, decisions, what's new, who's working
/insights/*
Analytics — Overview, usage, trends, member activity
/analytics/*
Search — Global full-text search
/search
Knowledge — CRUD, search, generate articles
/knowledge/*
Findings — Agent scan results, stats, dismiss, resolve
/findings/*
Agents — Agents, subscriptions, scans
/agents/*
Members — List, profiles, online status
/members/*
Notifications — List, mark read, preferences
/notifications/*
Webhooks — CRUD, deliveries, secret rotation
/webhooks/*
Settings — API keys, privacy, usage, invoices
/settings/*
Dashboard — Stats, activity, commits, sprint metrics
/dashboard/*

Real-time WebSocket Events

TeamContext uses Socket.IO for real-time updates. Connect with a JWT token for authentication.

const socket = io('https://api.teamcontext.ai', { auth: { token: 'your_jwt_token' } });

Events

turn:new New coding turn created status:update Team member status changed conflict:detected File overlap detected summary:new AI summary generated decision:new Technical decision extracted notification:new New notification task:created Task created task:updated Task status changed task:comment Comment added to task knowledge:new Knowledge articles generated

On connection, clients auto-join their team:{teamId} room to receive team-scoped events.

OAuth 2.0 / OIDC

TeamContext supports full OAuth 2.0 with PKCE for MCP client authentication. This enables AI tools to authenticate securely without storing credentials.

Endpoints

GET /.well-known/oauth-authorization-server POST /oauth/register # Dynamic client registration GET /oauth/authorize # Authorization (PKCE required) POST /oauth/token # Token exchange POST /oauth/revoke # Token revocation GET /oauth/consents # List user consents DELETE /oauth/consents/:id # Revoke consent

Supports authorization_code and refresh_token grant types. PKCE (code_challenge + code_verifier) is required for all authorization requests.