Authentication
How agents authenticate with Dailybot: API keys, OAuth, and identity for MCP and API access.
Agents and integrations need to authenticate with Dailybot to send check-ins, read context, or trigger workflows. Dailybot supports API keys and OAuth; the right method depends on whether you're building a backend agent, an MCP server, or a user-facing app.
API keys
For server-side agents and scripts, you typically use an API key (or token) that is tied to a Dailybot account or app. The key is sent in the request (e.g. Authorization: Bearer <token>) and determines which organization and permissions the agent has.
OAuth
For apps that act on behalf of a user (e.g. "connect your Dailybot" in another product), OAuth is used so the user authorizes access. The resulting token is then used like an API key for that user's context.
Full documentation
Scopes, token lifecycle, and request format are documented in the developer docs: Authentication. Use that page to obtain and use credentials for your agent or integration.