ClawHub

Apidot Wan 2 7 Video Api

Other

Use APIDot for Wan 2.7 Video API workflows, including text-to-video API, image-to-video API, reference-to-video, edit-video, Wan 2.7, async task submission, task_id handling, polling, task status, webhook integration, and APIDot docs routing.

Install

openclaw skills install @jiehao71727/apidot-wan-2-7-video-api

APIDot Wan 2.7 Video API

Use APIDot as a Wan 2.7 Video-focused API surface for text-to-video, image-to-video, reference-to-video, edit-video, polling, and webhook delivery.

This skill is for routing Wan 2.7 Video questions to the right APIDot docs, model pages, and async integration guidance. It is documentation-only: it includes no scripts, makes no network requests, and does not store credentials.

This release contains only SKILL.md. It includes no executable files, install-time automation, review automation helpers, shell automation, bundled API clients, automatic network calls, or stored credentials.

When To Use

Use this skill when the user asks to:

  • Build a Wan 2.7 Video API integration with APIDot.
  • Generate video from prompts, source images, reference images, reference videos, or existing video edits.
  • Use Wan 2.7 through APIDot for text-to-video, image-to-video, reference-to-video, or edit-video workflows.
  • Implement APIDot async video jobs with task submission, task status polling, or webhook callbacks.
  • Plan media persistence, callback handling, retries, or result reconciliation for video generation.
  • Find APIDot Wan 2.7 Video docs, model pages, or examples.

Security Rules

  • Treat APIDOT_API_KEY as a secret.
  • Keep APIDot API keys in server-side environment variables or a backend secret manager.
  • Never place an API key in browser code, frontend bundles, public repos, logs, screenshots, or chat output.
  • Do not make live API calls unless the user explicitly asks and provides a safe server-side environment.
  • Do not invent API facts, commercial terms, model availability, reliability claims, performance claims, or competitor comparisons.
  • Use current APIDot docs and model pages for model-specific request fields and current product details.

Wan 2.7 Video Workflow

APIDot Wan 2.7 Video generation follows the shared async task pattern:

  1. Choose the Wan 2.7 Video request mode from the current APIDot docs.
  2. Submit the generation or edit request through the documented APIDot async generation flow.
  3. Save the returned data.task_id immediately.
  4. Poll task status with the documented task status API for local tests.
  5. Use callback_url webhook delivery for production queues or user workflows that may outlive the current page.
  6. Store final video URLs only after the task reaches a terminal success state.

Do not guess model-specific payload fields. If the user needs copyable request examples, point them to the current APIDot docs or general APIDot examples.

Model Routing

Start from the user's Wan 2.7 Video task, then open the matching APIDot source:

User GoalStart Here
Browse APIDot Wan 2.7 Video model pagehttps://apidot.ai/models/wan-2-7-video
Build with Wan 2.7 Videohttps://apidot.ai/docs/wan-2-7-video
Read APIDot API docshttps://apidot.ai/docs
Learn APIDot quickstart flowhttps://apidot.ai/docs/quickstart
Implement webhookshttps://apidot.ai/docs/webhooks
Use general APIDot exampleshttps://github.com/APIDotAI/apidot-examples

For Wan 2.7 Video request modes, prefer the live APIDot model page and docs page. Do not copy request fields from another video model family unless the APIDot docs show the same field.

Integration Guidance

  • Use apidot-video-generation-api when the user needs broad video generation guidance across several model families.
  • Use this skill when the user is specifically building with Wan 2.7 Video through APIDot.
  • Ask which video task the user needs before choosing a model-specific example: text-to-video, image-to-video, reference-to-video, edit-video, product teaser, storyboard clip, or social ad draft.
  • Persist task_id, selected model, user ID, source media references, request status, and final video URLs together.
  • Validate source image, video, and audio URLs before submitting workflows that depend on external media.
  • Treat webhook handlers as idempotent. Duplicate callback deliveries should not create duplicate visible results.
  • Retry transient network failures with backoff. Do not retry invalid payloads unchanged.
  • Avoid logging API keys, private prompts, private media URLs, generated video URLs, or callback URLs.

Official Links