Teamday

Docs

Teamday API Documentation

Machine-readable Teamday API contract for agents, workspaces, chats, jobs, missions, MCP, events, idempotency, and rate limits.

Teamday API Documentation

Teamday exposes an agent-ready API for durable work: agents, workspaces, chats, jobs, missions, files, MCP tools, and long-running execution status.

Use the machine-readable contract first when building an integration:

ResourceURL
OpenAPI 3.1 spechttps://app.teamday.ai/api/openapi.json
Interactive API referencehttps://app.teamday.ai/api/reference
Agent-readiness manifesthttps://app.teamday.ai/api/agent-readiness
Well-known agent manifesthttps://app.teamday.ai/.well-known/teamday-agent-api
SDK and client exampleshttps://app.teamday.ai/api/sdk-examples
Versioning and deprecation policyhttps://app.teamday.ai/api/deprecation-policy
Rate-limit policyhttps://app.teamday.ai/api/rate-limits
OAuth authorization server metadatahttps://app.teamday.ai/.well-known/oauth-authorization-server
OAuth protected resource metadatahttps://mcp.teamday.ai/.well-known/oauth-protected-resource
OAuth protected resource metadata for /mcphttps://mcp.teamday.ai/.well-known/oauth-protected-resource/mcp

The public docs are also emitted for LLM ingestion:

ResourceURL
Documentation indexhttps://docs.teamday.ai/llms.txt
Full docs bodyhttps://docs.teamday.ai/llms-full.txt
Page Markdownhttps://docs.teamday.ai/api.md

Agent-Ready Guarantees

Teamday's API contract is designed around agent automation:

  • Scoped service-token auth for server-side automation and browser-session auth for the app.

  • OAuth 2.1 metadata for MCP clients, with PKCE, dynamic client registration, and the mcp scope.

  • Server-Sent Events for live chat and job output: /api/chats/{id}/events and /api/jobs/{id}/events.

  • Webhook event delivery for durable work state changes and successful JSON API mutations, with event subscriptions, stable event IDs, Teamday-Signature HMAC-SHA256 verification, delivery attempts, retry backoff, and owner-initiated redelivery from the durable ledger.

  • Replay on stream connect so clients can reconnect without losing the latest chat or job events.

  • Request IDs through X-Request-Id for support and log correlation.

  • Rate-limit transparency through X-RateLimit-*, standard RateLimit-*, and Retry-After headers.

  • Machine-readable rate-limit policy at /api/rate-limits, including identity order, burst behavior, retry examples, and enterprise tier semantics.

  • Idempotency keys on mutating JSON API requests so agents can retry safely after network failures.

  • Long-running jobs with explicit status endpoints and review/approve/cancel/resume actions.

  • Generated-client recipes and thin SDK source for TypeScript, Python, SSE streaming, and webhook verification at /api/sdk-examples, /api/sdk/typescript, and /api/sdk/python.

  • Versioning and deprecation policy with date-based versions, 180-day deprecation notice, and 365-day sunset notice.

  • Authentication

  • Endpoints

  • Error Reference

  • Best Practices

For service-specific APIs, see Newsletter API. For general guides, see the Guides section.