API Reference
Complete REST API reference for Dailybot: 318 endpoints across 27 groups, with parameters, request/response examples, and error codes.
The Dailybot REST API allows you to programmatically manage check-ins, users, teams, messages, and more. All endpoints accept and return JSON, use standard HTTP methods, and require API key authentication.
Base URL
All API requests use the following base URL:
https://api.dailybot.com/v1/Authentication Required
X-API-KEY header. See the Authentication page for details.Resources
The API is organized around the following resources. Click on a resource to see all available endpoints, parameters, and response examples.
Users
5 endpointsRead the org directory, look up user profiles, and update user metadata.
Organization
1 endpointRead the organization the current credential is scoped to.
Teams
7 endpointsList teams, manage team membership, add or remove members.
Invitations
6 endpointsInvite users (platform or guest), list and manage pending invitations.
Check-ins
14 endpointsCreate, configure, and archive check-ins; manage questions, schedule, participants, and responses.
Forms
15 endpointsCreate, configure, and archive forms; manage questions, workflow, and responses.
Report Channels
1 endpointList available chat channels for report delivery on forms and check-ins.
Templates
2 endpointsRetrieve pre-built check-in templates with rendered question variables.
Messaging
3 endpointsSend bot messages to users, teams, and channels; send emails; open conversations.
Kudos
4 endpointsGive kudos, list kudos, org-wide stats, wall of fame leaderboard.
Mood Tracking
1 endpointTrack team mood entries for wellbeing signal.
Important Dates
2 endpointsList and retrieve important dates (birthdays, anniversaries).
Automations
5 endpointsCreate, retrieve, update, and delete automations.
Webhooks
2 endpointsCreate webhook subscriptions and request sample event payloads.
Agents
14 endpointsFull agent surface: reports, health, messages, email, webhook, claim, and self-registration.
OAuth2
2 endpointsOAuth2 authorization and token endpoints for third-party apps.
Integrations
2 endpointsEvent and webhook callbacks used by first-party integrations.
Commands Platform
14 endpointsScheduling, storage, event subscriptions, activity feed, exchange tokens.
CLI (auth)
7 endpointsCLI-only OTP authentication endpoints and status.
Dailybot Plan (Beta)
Beta
Plan is in beta. Everything under /plan in the web app, the CLI and agent skill commands for projects, goals, boards and tasks, and the /v1/plan/ public API may change before general availability. Want to try it with your team? Write to support@dailybot.com.
Plan · Projects
Beta46 endpointsProjects group boards and carry health, status notes, milestones, members and saved views. Part of the Dailybot Plan API (Beta).
Plan · Goals
Beta13 endpointsGoals say what the work is for. They point at projects; nothing lives inside a goal. Part of the Dailybot Plan API (Beta).
Plan · Boards
Beta33 endpointsBoards and their workflow states, the one-call board snapshot, the delta feed, members, labels and saved views. Part of the Dailybot Plan API (Beta).
Plan · Tasks
Beta24 endpointsCreate, read, update, move, archive and restore tasks, one at a time or in bulk, plus relations, labels, participants and subscriptions. Part of the Dailybot Plan API (Beta).
Plan · Comments & files
Beta22 endpointsComments, reactions, attachments, and each task's activity feed and event log. Part of the Dailybot Plan API (Beta).
Plan · Home & search
Beta22 endpointsEntitlements, the home screen in one request, my tasks, favorites, inbox, activity, timeline, search, organization labels and milestones. Part of the Dailybot Plan API (Beta).
Plan · Notifications & reports
Beta23 endpointsThe notification catalogue, each person's switches and daily briefing, the organization's channel routes and scheduled reports, and the channels they post to. Part of the Dailybot Plan API (Beta).
Common Patterns
Pagination
Most list endpoints use limit/offset pagination. Use limit (default 250, max 250) and offset to navigate pages. Some endpoints (e.g. pending invitations) use page-based pagination with page and page_size (max 100).
Error Codes
The API uses standard HTTP status codes:
| Code | Status | Description |
|---|---|---|
| 200 | OK | Request succeeded |
| 201 | Created | Resource created successfully |
| 204 | No Content | Request succeeded, no response body |
| 400 | Bad Request | Invalid request body or parameters |
| 401 | Unauthorized | Missing or invalid API key |
| 403 | Forbidden | Insufficient permissions |
| 404 | Not Found | Resource not found |
| 429 | Too Many Requests | Rate limit exceeded |
| 500 | Server Error | Internal server error |
Error response format
Errors return a JSON body with detail (human-readable message) and code (machine-readable). Some include extra for context. When rate limited (429), the response includes a Retry-After header.
Rate limits
Authenticated requests: 60 requests/minute. Anonymous requests: 30 requests/minute.
Request Format
All requests must include the following headers:
curl -X GET "https://api.dailybot.com/v1/{endpoint}/" \
-H "X-API-KEY: your_api_key" \
-H "Content-Type: application/json" \
-H "Accept: application/json"