Schedule 50 videos at once across 11 platforms

There's no hard cap on batch size — you can submit 100, 500, or 1,000 video URLs in sequence. Practical limits come from the destination platforms: YouTube's 10K unit/day quota (or your BYOP project's 10K), TikTok's 100 daily uploads per account, Instagram's 200 calls/hour per Page. CodivUpload's queue paces requests to stay within each platform's limits without you managing it.

Yes. Each POST /v1/posts call accepts a scheduled_date in ISO 8601 UTC. Or pass schedule_best_time=true and CodivUpload picks the optimal hour from each connected account's last 90 days of analytics. Or omit both fields and the post goes out immediately. Mix and match across your batch.

Both. The dashboard's bulk-upload screen accepts a CSV or a folder drag, generates one queued post per row/file, and shows the same status grid as the API. The REST API exposes the same operations as POST /v1/posts calls. Most teams start in the dashboard and switch to the API when they want to wire a CMS/Airtable/Make pipeline into the upload flow.

The post lifecycle becomes partially_failed. Successful destinations stay published (they're not rolled back), failed destinations get a status=failed row with error_message. Use POST /v1/posts/:id/retry-failed to re-queue only the failed destinations after fixing the root cause — no duplicate posts on the platforms that already succeeded.

Pass a custom scheduled_date with progressive offsets (e.g. each video 15 minutes apart) to spread the load. The queue worker also auto-throttles per platform's rate limit — even if you submit 100 calls in 1 second, the worker spaces actual platform API calls to stay polite.

For files >100MB, use the 3-step presigned upload flow: POST /v1/upload-media/presign returns a signed URL, you PUT the file directly to the URL (browser→CDN, no proxy through CodivUpload's servers), then POST /v1/upload-media/finalize marks the upload complete. The returned CDN URL is then ready for POST /v1/posts.