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

5 endpoints

Read the org directory, look up user profiles, and update user metadata.

GETPATCH

Organization

1 endpoint

Read the organization the current credential is scoped to.

GET

Teams

7 endpoints

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

GETPOSTPATCHDELETE

Invitations

6 endpoints

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

GETPOSTPUTDELETE

Check-ins

14 endpoints

Create, configure, and archive check-ins; manage questions, schedule, participants, and responses.

GETPOSTPATCHPUTDELETE

Forms

15 endpoints

Create, configure, and archive forms; manage questions, workflow, and responses.

GETPOSTPATCHPUTDELETE

Report Channels

1 endpoint

List available chat channels for report delivery on forms and check-ins.

GET

Templates

2 endpoints

Retrieve pre-built check-in templates with rendered question variables.

GET

Messaging

3 endpoints

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

POST

Kudos

4 endpoints

Give kudos, list kudos, org-wide stats, wall of fame leaderboard.

GETPOST

Mood Tracking

1 endpoint

Track team mood entries for wellbeing signal.

POST

Important Dates

2 endpoints

List and retrieve important dates (birthdays, anniversaries).

GET

Workflows

5 endpoints

Create, retrieve, update, and delete automated workflows.

GETPOSTPATCHDELETE

Webhooks

2 endpoints

Create webhook subscriptions and request sample event payloads.

POST

Agents

14 endpoints

Full agent surface: reports, health, messages, email, webhook, claim, and self-registration.

GETPOSTDELETE

OAuth2

2 endpoints

OAuth2 authorization and token endpoints for third-party apps.

GETPOST

Integrations

2 endpoints

Event and webhook callbacks used by first-party integrations.

POST

Commands Platform

14 endpoints

Scheduling, storage, event subscriptions, activity feed, exchange tokens.

GETPOSTPUTDELETE

CLI (auth)

7 endpoints

CLI-only OTP authentication endpoints and status.

GETPOST

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"