ItemlumePRODUCT CREATIVE / PRODUCTION AND HANDOFF
Why Doesn't Claid's Studio Prompt Assistant Automatically Improve My API Video Request?
Claid Studio's Prompt Assistant is a separate application feature. It can expand a short creative direction for review, but API video requests use the prompt text actually submitted. Do not assume an API request receives the same automatic prompt expansion as a Studio workflow.
Separate Studio Assistance From API Submission
Studio provides a Prompt Assistant that can expand a brief direction into a more developed prompt. The merchant should review that expanded text before treating it as an approved production instruction.
The API uses the prompt supplied in its request. A short API prompt therefore should not be assumed to contain additional directions produced by Studio's assistant. This is an application-workflow distinction, not evidence that the underlying generation settings or results are otherwise identical.
Maintain Three Distinct Versions of the Instruction
The original brief records the merchant's business objective, such as showing a product opening before revealing its contents. The approved prompt records the reviewed creative instructions intended for generation. The request text records what was actually submitted through the selected entry point.
These versions may differ legitimately, but differences must be traceable. If Studio expands a direction and a reviewer approves it, that approved text does not automatically appear in a later API request. Decision branch: Compare the submitted text with the approved prompt before investigating unrelated generation behavior.
Illustrative Exercise: Two Video Production Routes
Illustrative exercise — fictional workflows, not executed Claid Studio sessions or API calls. Input A begins with a short merchant brief for a product reveal. A Studio operator uses Prompt Assistant, reviews the expanded description, and records the approved version.
Input B uses the same original brief through an API workflow, but the submitted request contains only the short initial text. The two inputs are not instruction-equivalent. Decision branch: If the team intended to use the reviewed Studio wording, compare and reconcile the request text before submission. Do not assume equivalent outputs even after the text matches.
| Instruction record | Purpose | Handoff check |
|---|---|---|
| Original merchant brief | Define the intended product story | Confirm business requirements remain accurate |
| Approved prompt and actual request text | Define reviewed instructions and submitted content | Compare versions and record any differences |
Review the Production Record Before Diagnosing Results
Assign a version identifier to the original brief, approved prompt, and submitted request text. Record who reviewed each revision and which version was authorized for the intended video task.
When results differ between Studio and API workflows, first establish whether their submitted instructions actually matched. Even matching text does not guarantee reproducible video results or identical model parameters. Review the resulting video separately for product identity, intended action, and completeness. Keep credentials and private API information outside the editorial handoff.
Illustrative Exercise — Brief, Approved Prompt, and Submitted Request
These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.
| Fictional workflow | Original brief | Approved instruction | Actual submission | Decision branch |
|---|---|---|---|---|
| A: Studio-assisted product reveal | Show a product opening | Reviewed expanded Studio prompt | Approved text selected for Studio generation | Preserve approved wording and its version identifier |
| B: API product reveal | Show a product opening | Previously approved expanded prompt exists | Only the original short brief was submitted | Reconcile submitted text with the approved version before diagnosing results |
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
- Image to Video — Claid Help · Reviewed
Frequently asked questions
Does the API automatically apply Studio's Prompt Assistant?
No. The official workflow distinguishes Studio's assistant from API submission. API requests use the prompt text provided in the request.
Will copying an approved Studio prompt into an API request reproduce the same video?
Not necessarily. Matching prompt text resolves one instruction difference, but the documentation does not establish identical settings or reproducible outputs across the two entry points.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in Itemlume.
Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.
Explore asset creation tools Check pricing and credits