Changelog

Telegram is now a first-class publish destination. Connect a bot with POST /v1/connections/telegram/connect and jobs can deliver videos to any channel where the bot is an administrator.

• Bot connections are verified at connect time — invalid tokens fail with INVALID_BOT_TOKEN instead of at publish.
• Channels are resolved from the bot's admin list; pass chatId in the job payload to target a specific channel.
• Caption, spoiler flag, and disable_notification map onto the job's title and options fields.

Pass webhookUrl when creating a job to receive a signed callback on every status transition — no more polling GET /v1/publishing/jobs/:id.

• Every delivery carries X-LynCut-Signature — an HMAC-SHA256 of the raw body keyed on your webhook secret.
• Failed deliveries retry up to 5 times with exponential backoff; dedupe on X-LynCut-Delivery.
• Callbacks fire for COMPLETED, FAILED, and CANCELED terminal states.

The asset catalog behind the LynCut editor is now public. GET /v1/assets, /v1/assets/categories, /v1/assets/resolve, and /v1/assets/package require no API key and are safe to call from browsers.

Resolve endpoints return a 302 redirect to a signed CDN URL — cache the redirect target, not the resolver response.

Large exports no longer need a single multipart request. POST /v1/publishing/upload-intents returns an intent id and resumable upload URL; clients push chunks with plain PUT requests and reference the finished upload as mediaKey on the job.

• Intents expire after 24 hours — abandoned uploads are cleaned up automatically.
• Chunk size is client-chosen; re-issue the intent call to resume after a network failure.

Two new OAuth providers join the connections roster: Threads (Meta) and LinkedIn. Both use the standard GET /v1/connections/:provider/connect flow — no provider-specific endpoints.

• LinkedIn supports member posts and organization pages — pass organizationId in the job payload to post as a Page.
• Threads requests the threads_content_publish scope during OAuth.

GET /v1/sessions lists the account's active sessions with device and last-seen metadata. DELETE /v1/sessions/:id revokes one; POST /v1/sessions/revoke-others keeps the caller's session and kills the rest.

OAuth connections for YouTube, TikTok, Facebook, and X are now stable. GET /v1/connections returns each connection's scopes and token status so you can warn users before a job fails on an expired grant.

• Tokens refresh automatically; status: EXPIRED means the user must reconnect.
• Deleting a connection immediately revokes queued-but-unpublished jobs for it.

Publishing moved to an async job model. POST /v1/publishing/jobs returns 202 with a job id; the job progresses QUEUED → UPLOADING → PROCESSING → COMPLETED, with FAILED carrying a provider-specific errorCode.

POST /v1/publishing/jobs/:id/retry re-queues a failed job; POST /v1/publishing/jobs/:id/cancel stops a queued one. Terminal jobs can't be retried or canceled.

The first public release of the LynCut API. Create API keys in the dashboard, call https://api.lyncut.com with the x-lyncut-api-key header, and manage connections, sessions, profile, and storage under /v1.

GET /v1/storage/usage reports bytes used and the account quota — the same numbers the dashboard's storage meter reads. Part of the early-access program before the public beta.