Skip to content
ExplainerAdminMember

Public API overview

Public API overview

Dailybot has a public API for supported team coordination and integration tasks. You can use it to work with resources documented in the developer portal, including check-ins, forms, workflows, kudos, messages, users, teams, integrations, and agent operations.

Start with the developer portal

Use the API quick start to choose an authentication method and make a first request. Then use the API reference to confirm that the operation you need is available.

The reference is the source of truth for endpoint paths, request fields, response shapes, permissions, and examples. Do not infer an endpoint from a Help Center article or from a similarly named feature in the web app.

Choose API, CLI, or agent skill

  • Use the API when your application or service sends HTTP requests and needs direct control over a supported resource.
  • Use the CLI for terminal workflows, local scripts, and supported headless tasks.
  • Use the agent skill pack when a compatible AI coding agent should select and run a supported Dailybot action through a guided skill.

All three use the same public developer platform, but their authentication and command surfaces differ. See Developer tools overview for a comparison.

Authenticate safely

Read API authentication before creating or using a credential. Keep credentials in a secret manager or local authentication store. Never place a key in source code, a committed configuration file, a support ticket, or a chat message.

The authenticated user and organization determine what a request can access. A successful login does not bypass the permissions of the account behind the credential.

Build against the documented contract

Use the current API reference for requests and the errors guide for failure handling. Validate input before sending it, handle non-success responses explicitly, and log enough request context to diagnose a problem without logging credentials or sensitive data.

For event-driven integrations, review Webhooks and events instead of repeatedly requesting the same resource. For pipeline use, see Use Dailybot in CI/CD.

If the operation you need is not in the reference, contact Dailybot support with the intended outcome. Do not build against an undocumented path or field.