Apidot Kling O3 Api

Use APIDot for Kling O3 API workflows, including Kling O3 Standard, Kling O3 Pro, Kling O3 4K, text-to-video API, image-to-video API, reference video generation, multi-shot video, Native Audio, async task submission, task_id handling, polling, task status, webhook integration, and APIDot docs routing.

jiehao71727@jiehao71727

Install

openclaw skills install @jiehao71727/apidot-kling-o3-api

APIDot Kling O3 API

Use APIDot as a Kling O3-focused API surface for text-to-video, image-to-video, reference-guided video, multi-shot planning, Native Audio workflows, polling, and webhook delivery.

This skill is for routing Kling O3 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 Kling O3 API integration with APIDot.
Generate videos from prompts, source images, or reference media.
Use Kling O3 Standard, Kling O3 Pro, or Kling O3 4K through APIDot.
Plan reference-guided video, multi-shot clips, Native Audio behavior, polling, or webhook callbacks.
Implement APIDot async Kling O3 jobs with task submission, task status polling, or webhook delivery.
Find APIDot Kling O3 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.

Kling O3 Workflow

APIDot Kling O3 generation follows the shared async task pattern:

Choose the Kling O3 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 Kling O3 task, then open the matching APIDot source:

User Goal	Start Here
Browse APIDot Kling O3 model page	https://apidot.ai/models/kling-o3
Build with Kling O3	https://apidot.ai/docs/kling-o3
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 Kling O3 model routing, request planning, and async workflow notes.

For Kling O3 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-kling-3-0-api when the user asks specifically for Kling 3.0.
Use this skill when the user is specifically building with Kling O3 through APIDot.
Ask which video task the user needs before choosing a model-specific example: text-to-video, image-to-video, reference-guided video, multi-shot scene, Native Audio, storyboard clip, product teaser, or social ad draft.
Persist task_id, selected model, user ID, source media references, request status, and final video URLs together.
Validate source image and reference media 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.