Skip to content

API Reference

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:

text 
https://api.dailybot.com/v1/

Authentication Required

Every request must include your API key in the 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 & Organization

6 endpoint s

Manage users, get /me and organization, update profiles and metadata, invite members.

GET PATCH POST

Teams

5 endpoint s

List teams, manage team membership, add or remove members.

GET POST PATCH DELETE

Invitations

7 endpoint s

Invite users (platform or guest), list and manage pending invitations.

GET POST DELETE

Checkins & Forms

11 endpoint s

Create and manage check-ins, browse templates and forms, retrieve responses.

GET POST PATCH DELETE

Messaging

3 endpoint s

Send messages to users, teams, and channels. Send emails and open conversations.

POST

Kudos

4 endpoint s

List and send kudos for team recognition.

GET POST PATCH

Workflows

8 endpoint s

Create, manage, and monitor automated workflows and execution logs.

GET POST PUT PATCH DELETE

Webhooks API

3 endpoint s

Create and manage webhook subscriptions and request sample payloads.

POST DELETE

Mood Tracking

2 endpoint s

Get and submit mood scores for wellbeing tracking.

GET POST

Important Dates

2 endpoint s

List and create important dates (birthdays, anniversaries).

GET POST

Agent Reports

1 endpoint

Submit activity reports from bots and CI/CD pipelines.

POST

Commands Platform

10 endpoint s

Scheduling, storage, events, activity, and exchange tokens.

GET POST PUT DELETE

CLI

6 endpoint s

CLI authentication and check-in update submission.

GET POST

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:

Standard request 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"