Metadata-Version: 2.5
Name: fancy-youtube
Version: 0.2.1
Summary: YouTube for Python — the service descriptor, its faker, its webhook verification, and one function per operation. Plain HTTP; no vendor SDK.
Project-URL: Homepage, https://github.com/Fancy-Friends/youtube
Project-URL: Issues, https://github.com/Fancy-Friends/youtube/issues
Project-URL: Source, https://github.com/Fancy-Friends/youtube
Author: Particle Academy
License-Expression: MIT
License-File: LICENSE
Keywords: api,connector,fancy-flow,marketing,particle-academy,youtube
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Topic :: Software Development :: Libraries
Classifier: Typing :: Typed
Requires-Python: >=3.11
Description-Content-Type: text/markdown

# YouTube

YouTube for [fancy-flow][flow] — as **four imported, versioned packages**, one
per runtime. Not vendored source: a copy cannot be upgraded, and third-party APIs
change.

[flow]: https://github.com/Particle-Academy/fancy-flow

| Runtime | Package | Install |
|---|---|---|
| Authoring surface (every host) | `@particle-academy/youtube-ui` | `npm install @particle-academy/youtube-ui` |
| Node | `@particle-academy/youtube-js` | `npm install @particle-academy/youtube-js` |
| PHP 8.4+ | `particle-academy/youtube-php` | `composer require particle-academy/youtube-php` |
| Python 3.11+ | `fancy-youtube` | `pip install fancy-youtube` |

The `ui` package is the editor surface and is React on every host — a PHP or
Python project installs it *and* its own runtime package, and never the `js` one.

## What it costs you

One dependency: `@particle-academy/fancy-connector-core` (or
`particle-academy/fancy-connector-core` on Composer), which the `js` and `php`
packages pull in themselves. The Python package has **zero** runtime
dependencies.

**No YouTube SDK.** Plain HTTP, deliberately: a vendor SDK is third-party code
subject to the kit's full approval bar, and one per provider is hundreds of
dependencies nobody is tracking.

## Setting it up

Everything below is generated from `provider/manifest.json`, so it cannot disagree with what the packages do.

### Credentials

A YouTube connection holds 4 values.

**Two kinds of value, and mixing them up matters.** A `provider` credential is ONE value for the whole installation — an OAuth app's client secret serves every connected account. An `account` credential is one per connected account. A host that stores the second where it stores the first lets one account's credentials reach another's.

| Field | Scope | Secret | Where it comes from |
|---|---|---|---|
| **OAuth client ID** | per installation | not secret | From Google Cloud Console. One value for the whole installation. |
| **OAuth client secret** | per installation | **secret** | The client secret for the same OAuth app. |
| **Access token** | per connected account | **secret** | Per connected YouTube account; expires after one hour. |
| **Refresh token** | per connected account | **secret** | Per connected YouTube account; the host uses it to refresh the access token. |

### Authorising

YouTube uses OAuth2 (authorization_code). The package DECLARES the exchange; the HOST performs it — a consent screen needs a browser, a redirect URI and somewhere to persist the result, and all three belong to the host.

- **Authorize URL** — https://accounts.google.com/o/oauth2/v2/auth
- **Token URL** — https://oauth2.googleapis.com/token
- **Scopes** — `https://www.googleapis.com/auth/youtube.force-ssl`
- **Access token lifetime** — 3600 seconds (1 hours). A host that never refreshes works all afternoon and is broken by morning.

The refresh tokens do **not** rotate: the same one is reusable, so a refresh may safely be retried and may run concurrently. Stated rather than assumed, because the opposite — a provider that spends the token and revokes the grant on a replay — looks identical until it happens.

### The estate

**YouTube has no test estate, and somebody checked.** Everything this connector does is real. Use the faker to build against it.

> YouTube has no sandbox. Every live-mode add changes a real playlist; use the faker during development and remove live test items afterward.

## What it can do

### Actions

#### `playlist_item_insert` — YouTube playlist item

Add a video to a YouTube playlist.

`POST /youtube/v3/playlistItems` · **unsafe to replay** — a retried durable run does it TWICE

| Input | Required | What it is |
|---|---|---|
| `playlistId` | yes | The YouTube id of the playlist to add the video to. |
| `videoId` | yes | The YouTube id of the video to add. |

## Run it before you have credentials

Every operation ships a **faker**, whether or not YouTube has a sandbox. Set a
node's mode to `fake` and it returns the shape YouTube actually publishes — the
same field names, deterministically — so you can wire the downstream nodes before
touching an account, a key, or a network.

## This repository is generated

`provider/` is the source. Everything under `packages/` is emitted from it and
**must not be hand-edited** — CI regenerates and diffs on every push, and the
next protocol sync destroys anything it finds. See [`AGENTS.md`](AGENTS.md).

## Two namespaces, which do not match on purpose

The repo is `github.com/Fancy-Friends/youtube`; the packages publish under
`particle-academy`. Nothing derives one from the other — the names come from
weaver's `friends.json` and nowhere else.

## Licence

MIT.
