Developer tools overview
Dailybot’s developer tools let you connect team coordination to your own software, scripts, pipelines, and AI coding agents. Start with the tool that matches who will run the task and how much control the integration needs.
Choose the right tool
- Public API: Use HTTP requests when an application or service needs direct access to supported Dailybot resources. The API reference is the source of truth for available endpoints and request fields.
- CLI: Use terminal commands for local scripts, operational tasks, and headless environments. See the CLI guide for installation, authentication, and supported commands.
- Agent skill pack: Use the skill pack when an AI coding agent should report progress, complete supported team actions, or use Dailybot through guided workflows. Start with Install and use the Dailybot agent skill pack.
- Webhooks and interactive callbacks: Use event delivery when your application needs to react to activity instead of polling. Follow the webhooks guide and the relevant endpoint reference.
- Custom commands and workflows: Use these when a person or system should trigger a saved Dailybot flow. Check the developer recipes for supported patterns.
Start with authentication
Each tool has an authentication flow. Do not copy a credential into source code, chat, an article, or a committed configuration file. Read API authentication before choosing between an API key and a CLI session.
For unattended jobs, store credentials in the secret manager provided by your CI or hosting platform. For a developer workstation, use the interactive login flow documented for the CLI.
Use the detailed reference for contracts
Help Center articles explain which capability to use and how the pieces fit together. The developer portal owns endpoint paths, headers, request fields, CLI flags, error codes, and current examples. When a Help Center summary and a reference page appear to differ, follow the reference and contact support so we can correct the summary.