Docs · api
Connections And MCP
Current Teamday API guidance for external tools, data connections, MCP servers, and webhook events.
Connections And MCP
Teamday connects agents to external systems through MCP servers, workspace resources, org secrets, and webhooks.
Use the OpenAPI spec as the source of truth:
https://app.teamday.ai/api/openapi.json
MCP Endpoint
| Method | Path | Purpose | Auth |
|---|---|---|---|
POST | /mcp | Send MCP JSON-RPC or Streamable HTTP messages | OAuth mcp scope |
GET | /mcp | Open an MCP Streamable HTTP session | OAuth mcp scope |
DELETE | /mcp | Close an MCP session | OAuth mcp scope |
OAuth metadata:
https://app.teamday.ai/.well-known/oauth-authorization-server
https://app.teamday.ai/.well-known/oauth-protected-resource
Data Blocks
Workspace data-block queries use:
POST /api/workspaces/{id}/data-blocks/query
Queries are read-only and scoped to the organization and workspace.
Webhook Events
Configure durable work event delivery through:
PUT /api/messaging-integration
GET /api/messaging-integration/deliveries
POST /api/messaging-integration/deliveries/{id}/redeliver
POST /api/messaging-integration/signing-secret/rotate
Webhook deliveries include stable event IDs and Teamday-Signature HMAC-SHA256 verification. Configure event_types as exact event names or wildcard families such as job.*; an empty list means all events. Every send attempt is recorded in the delivery ledger with status, HTTP status, attempt number, duration, and redacted destination host. Owners can redeliver a retained event from the ledger; Teamday signs the replay with the current webhook signing secret and records the new attempt.