Automate retros, health checks and actions with the TeamRetro API
The TeamRetro REST API and webhooks let you automate retrospectives, health checks, actions and teams — and push events straight into your own systems. Built for AI agents, too.
One REST API across retros, health checks, actions and teams
Pull retro summaries into your reports, sync actions with your tracker, provision teams from your HR system — whatever your workflow needs. Authenticate with a bearer token and you’re away:
curl https://developer.teamretro.com/api/v1/actions \
-H "Authorization: Bearer $TEAMRETRO_API_KEY" What you can build
Teams & people
List and manage teams, members and roles. Provision users from your own systems.
Actions & agreements
Create, update and close actions; read and maintain working agreements.
Meetings & health
Read retrospective, health-check and estimation metadata, plus health models, to feed your reporting.
Report exports
Download CSV exports — team activity, action activity, retro and health-check activity, team health and users.
Authentication & access
Bearer keys, scoped
Create keys under Settings → API & SCIM with Read, Write or SCIM scope. Send them as Authorization: Bearer <key>. Revoke any key the moment you need to.
Team-level on every plan
Team-scoped keys work on all plans. Enterprise unlocks account-wide, cross-team keys plus SCIM provisioning — the same line we draw for cross-team insights over MCP. Organization owners can disable API & MCP access for the whole account at any time.
Webhooks — know the moment it happens
Don’t poll. Point TeamRetro at an endpoint and we’ll push a signed event as soon as something changes — a retro or health check completes, an action is created, reassigned or closed, an agreement changes, a member joins, or someone is @mentioned.
{
"event": "action.completed",
"timestamp": "2026-06-09T10:30:00.000Z",
"data": { "action": { "id": "…", "title": "Fix flaky CI", "team": "Mobile" } }
}Per-team, self-serve
Configure under Team → Settings → Integrations. Choose the events, set your endpoint, get an auto-generated signing secret and send a test event.
Signed & verifiable
Every delivery carries an X-TeamRetro-Signature (HMAC-SHA256) and a unique delivery id, so you can verify authenticity and de-duplicate.
Reliable delivery
HTTPS only, 30-second timeout, and automatic retries (immediate, then 1m, 5m, 30m and 2h) before a failing endpoint is paused.
Built for AI agents, too
Quickstart
List a team’s open actions, then close one:
# Find open actions for a team
curl "https://developer.teamretro.com/api/v1/actions?status=open" \
-H "Authorization: Bearer $TEAMRETRO_API_KEY"
# Mark an action complete
curl -X PATCH https://developer.teamretro.com/api/v1/actions/$ACTION_ID \
-H "Authorization: Bearer $TEAMRETRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "status": "completed" }'The full reference — every resource, filter and field — is at developer.teamretro.com/docs.
Questions, answered
Who can use the API?
How do I authenticate?
Authorization: Bearer <key> header. Keys are scoped Read, Write or SCIM when you create them, and can be revoked at any time.Webhooks or polling?
Is there an AI / MCP option?
Where are the full API docs?
Enterprise-grade security, compliance, and control
TeamRetro is SOC 2 Type 2 accredited by an independent auditor who has evaluated our policies, product, platform, and infrastructure in accordance with the Standard on Assurance Engagements (ASAE 3150).
-
GDPR compliance and regional hosting (US & EU)
-
Single Sign-On (SSO) via SAML
-
SCIM for scalable user provisioning
-
Audit logs available on request
We maintain 99.9% uptime, with fast-response SLAs to ensure your teams stay productive and supported. Status dashboard