Seedance 3.0

Bot API Docs

Integrate Seedance through the Bot API

Use the public bot API docs to create keys, upload assets, create video tasks, and poll results from scripts, bots, and agent workflows.

Key points

API keysAuthenticated access

Bot and agent workflows start from account-managed API credentials.

UploadsTask pipeline

Automation can upload assets, create tasks, and poll results through one public docs route.

AgentsMachine-oriented docs

The route is written for scripts, bots, and autonomous workflow systems.

Highlights

  • Create and manage API keys from the signed-in account panel.
  • Upload reference assets, create tasks, and poll result status.
  • Copy a machine-oriented Markdown guide for autonomous agents.
  • Use one public documentation route across all supported Sunday locales.

What the API docs explain

How authentication works

The docs explain API key creation and how authenticated routes map back to the same account and Star system as the frontend.

How the task pipeline works

Automation can upload media, create tasks, poll task status, and retrieve final results using documented endpoints.

How docs stay discoverable

Even before the full interactive docs hydrate, crawlers can read that Seedance exposes a public automation surface.

Public Sunday routes

About this route

The bot API docs route is the public Seedance reference for scripts, workflow tools, and agent integrations that need authenticated video generation access.

The interactive app renders the full documentation experience, while the static page keeps the route indexable and discoverable for crawlers and lightweight clients.

Bot API questions

Who should read the Bot API docs route?

It is meant for developers, bot builders, and agents that need direct programmatic access to uploads, task creation, status polling, and user summaries.

Why include a static API route summary?

Documentation routes often win search traffic. A static summary makes the page indexable even if the full docs UI depends on JavaScript.