The DailyTube API gives your applications programmatic access to the same briefing engine that powers DailyTube: feeds, daily summaries, chat, delivery channels, and account management — 35 endpoints across nine surfaces.
## What you can do
- **Read and search briefings** — list, search, and open daily digests, including your saved and shared ones.
- **Generate summaries on demand** — from URLs, pasted text, or your connected feeds.
- **Chat with your digests** — send messages, attach briefings, retry or approve assistant actions.
- **Manage the account** — feeds, delivery channels, settings, subscription, and support — the same operations the web apps expose.
## Base URL
```endpoint
GET https://api.daily-tube.com/v1
```
All paths in this documentation are relative to `https://api.daily-tube.com/v1`.
## Conventions
- **JSON everywhere.** Requests and responses are JSON; send `Content-Type: application/json`.
- **Envelopes.** Success responses carry `{ "data": …, "request_id": "…" }`. Errors carry `{ "error": { "code", "message" }, "request_id": "…" }` — `code` is a stable machine string (see [Errors](/docs/errors)).
- **Ownership.** Every keyed endpoint is scoped to the key's account. Another account's resource is indistinguishable from a nonexistent one (`404`).
- **IDs.** Briefing ids are strings; shared briefings expose an 8-character hex `short_id` usable by anyone with the link.
## Where next
> Start with the [Quickstart](/docs/quickstart) — one request, under a minute. Then [Authentication](/docs/authentication) and [Rate limits](/docs/rate-limits) before you build anything real.
Introduction
The DailyTube API gives your applications programmatic access to the same briefing engine that powers DailyTube: feeds, daily summaries, chat, delivery channels, and account management — 35 endpoints across nine surfaces.
What you can do
• Read and search briefings — list, search, and open daily digests, including your saved and shared ones.
• Generate summaries on demand — from URLs, pasted text, or your connected feeds.
• Chat with your digests — send messages, attach briefings, retry or approve assistant actions.
• Manage the account — feeds, delivery channels, settings, subscription, and support — the same operations the web apps expose.
Base URL
GET https://api.daily-tube.com/v1
All paths in this documentation are relative to https://api.daily-tube.com/v1.
Conventions
• JSON everywhere. Requests and responses are JSON; send Content-Type: application/json.
• Envelopes. Success responses carry { "data": …, "request_id": "…" }. Errors carry { "error": { "code", "message" }, "request_id": "…" } — code is a stable machine string (see Errors (/docs/errors)).
• Ownership. Every keyed endpoint is scoped to the key's account. Another account's resource is indistinguishable from a nonexistent one (404).
• IDs. Briefing ids are strings; shared briefings expose an 8-character hex short_id usable by anyone with the link.
Where next
Start with the Quickstart (/docs/quickstart) — one request, under a minute. Then Authentication (/docs/authentication) and Rate limits (/docs/rate-limits) before you build anything real.
Get started / Introduction
Introduction
What the DailyTube API is, who it's for, and what you can build with it.
The DailyTube API gives your applications programmatic access to the same briefing engine that powers DailyTube: feeds, daily summaries, chat, delivery channels, and account management — 35 endpoints across nine surfaces.
What you can do
- Read and search briefings — list, search, and open daily digests, including your saved and shared ones.
- Generate summaries on demand — from URLs, pasted text, or your connected feeds.
- Chat with your digests — send messages, attach briefings, retry or approve assistant actions.
- Manage the account — feeds, delivery channels, settings, subscription, and support — the same operations the web apps expose.
Base URL
GEThttps://api.daily-tube.com/v1api.daily-tube.com/v1
All paths in this documentation are relative to https://api.daily-tube.com/v1.
Conventions
- JSON everywhere. Requests and responses are JSON; send
Content-Type: application/json. - Envelopes. Success responses carry
{ "data": …, "request_id": "…" }. Errors carry{ "error": { "code", "message" }, "request_id": "…" }—codeis a stable machine string (see Errors). - Ownership. Every keyed endpoint is scoped to the key's account. Another account's resource is indistinguishable from a nonexistent one (
404). - IDs. Briefing ids are strings; shared briefings expose an 8-character hex
short_idusable by anyone with the link.
Where next
Start with the Quickstart — one request, under a minute. Then Authentication and Rate limits before you build anything real.