Apidot Hailuo 02 Api

Use APIDot for Hailuo 02 API workflows, including MiniMax Hailuo 02, Hailuo 02 Pro, text-to-video API, image-to-video API, first frame and last frame guidance, physics-aware short video, async task submission, task_id handling, polling, task status, webhook integration, and APIDot docs routing.

jiehao71727@jiehao71727

Install

openclaw skills install @jiehao71727/apidot-hailuo-02-api

APIDot Hailuo 02 API

Use APIDot as a Hailuo 02-focused API surface for text-to-video, image-to-video, first-frame guidance, first-and-last-frame guidance, polling, and webhook delivery.

This skill is for routing Hailuo 02 questions to the right APIDot docs, model pages, reference notes, and async integration pattern. It is documentation-only: it includes no scripts, makes no network requests, and does not store credentials.

This release contains SKILL.md plus non-executable notes in references/api.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 Hailuo 02 API integration with APIDot.
Generate short videos from prompts, a first frame, or first-and-last-frame guidance.
Use Hailuo 02 or Hailuo 02 Pro through APIDot.
Plan text-to-video, image-to-video, frame-guided video, polling, or webhook callbacks.
Implement APIDot async Hailuo 02 jobs with task submission, task status polling, or webhook delivery.
Find APIDot Hailuo 02 docs, model pages, or general APIDot 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.

Hailuo 02 Workflow

APIDot Hailuo 02 generation follows the shared async task pattern:

Choose the Hailuo 02 model entry and request mode from the current APIDot docs.
Submit the video generation request through the documented APIDot async generation flow.
Save the returned data.task_id immediately.
Poll task status with the documented task status API for local tests.
Use callback_url webhook delivery for production queues or user workflows that may outlive the current page.
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 Hailuo 02 task, then open the matching APIDot source:

User Goal	Start Here
Browse APIDot Hailuo 02 model page	https://apidot.ai/models/hailuo-02
Build with Hailuo 02	https://apidot.ai/docs/hailuo-02
Read APIDot API docs	https://apidot.ai/docs
Learn APIDot quickstart flow	https://apidot.ai/docs/quickstart
Implement webhooks	https://apidot.ai/docs/webhooks
Use general APIDot examples	https://github.com/APIDotAI/apidot-examples

Use references/api.md for a local, non-executable summary of Hailuo 02 model routing, request planning, and async workflow notes.

For Hailuo 02 variants and 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 apidot-hailuo-2-3-api when the user asks specifically for Hailuo 2.3.
Use this skill when the user is specifically building with Hailuo 02 through APIDot.
Ask which video task the user needs before choosing a model-specific example: text-to-video, first-frame video, first-and-last-frame 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 URLs before submitting workflows that depend on frame guidance.
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.