creator-publish
Official-API publishing and scheduling for creator tools. No scraping, no unofficial endpoints — uploads only, through each platform's blessed API. Every adapter supports dry_run for safe testing.
Extracted from ShortSmash (2026-10-19) into a shared package so every creator tool benefits from the same fixes.
Platforms
YouTube (Shorts included), TikTok, Instagram Reels, X, Threads, Bluesky, LinkedIn, Pinterest, Facebook profile + Page.
Install
pip install creator-publish
pip install "creator-publish[youtube]" # for YouTube uploads (google client libs)
Use
from pathlib import Path
from creator_publish.publish import publish
from creator_publish import schedule
# post now (dry_run=True to test without posting)
result = publish("youtube", Path("clip.mp4"), title="POV: ...",
description="...", hashtags=["#pov"],
dry_run=True)
# or schedule it in plain English
job = schedule.schedule_video(Path("clip.mp4"), when="Friday 6pm",
platforms=["youtube", "tiktok"],
title="POV: ...")
schedule.worker() runs the durable SQLite queue (APScheduler, survives restarts, 3 retries with backoff).
Config
Secrets live in the environment (never written to disk by us):
| Platform | Needs |
|---|---|
| youtube | ~/.creator-publish/youtube_client.json (OAuth client) — token cached after first browser grant |
| tiktok | TIKTOK_ACCESS_TOKEN |
IG_ACCESS_TOKEN, IG_USER_ID (+ public video_url — Meta fetches server-side) |
|
| x | X_API_KEY, X_API_SECRET, X_ACCESS_TOKEN, X_ACCESS_SECRET |
| threads | THREADS_USER_ID, THREADS_ACCESS_TOKEN |
| bluesky | BSKY_HANDLE, BSKY_APP_PASSWORD |
LINKEDIN_ACCESS_TOKEN |
|
PINTEREST_ACCESS_TOKEN, PINTEREST_BOARD_ID |
|
FB_ACCESS_TOKEN / FB_PAGE_ID + FB_PAGE_ACCESS_TOKEN |
Set CREATOR_PUBLISH_HOME to share a home dir with another tool (ShortSmash sets it to ~/.shortsmash so existing tokens keep working).
License
MIT.
Metadata
Release files for creator-publish 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| creator_publish-0.1.0.tar.gz | 16.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| creator_publish-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.2 kB
Release files / creator_publish-0.1.0.tar.gz
| Download URL | creator_publish-0.1.0.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f2384544b8683efe8f10a67bd6eda9221940d150e31f85584fb07a139a4dd904
|
|
BLAKE2b-256 checksum How to use checksums |
074154aee48385a0db73cb7bb2ba73e2381d5578d3ea71b67dca304a02745677
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / creator_publish-0.1.0-py3-none-any.whl
| Download URL | creator_publish-0.1.0-py3-none-any.whl |
|---|---|
| Size | 22.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e4b38347b98d2d6d7183c9bd1f6e41d700c9f9781322d8ba09e91ec00d7de7e
|
|
BLAKE2b-256 checksum How to use checksums |
d173d684983979562293e0bea8abfe39bcae9bf0dd7e1226e18427f4cb860e04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for creator-publish 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for creator_publish-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.