Video Effects Romantic Lift
Playground
Try it on WavespeedAI!Convert photos into romantic princess-carry image-to-video clips with natural motion and emotion for beautiful clips. Ready-to-use REST inference API, best performance, no coldstarts, affordable pricing.
Features
Romantic Lift Effect
Requirements
Number of Images
- Mandatory
- Only one image upload supported
Number of People
- Only dual-person photo supported
Image Requirements
- Full-body photo of two subjects with visible feet and thighs for better results
Prompt
- Mandatory
- Format should remain unchanged as much as possible (details refer to the “prompt” parameter in the request example)
- If custom requirements exist, modify the prompt without altering the structure and majority of the content
Effect Boundaries
- Close proximity between subjects may cause limb articulation errors
Best Practices
- Use clear, full-body photos
- Ensure both subjects are clearly visible
- Make sure feet and thighs are visible in the photo
- Keep the default prompt structure
- Follow the gender-based lifting rules in the prompt
- Maintain appropriate distance between subjects
Authentication
For authentication details, please refer to the Authentication Guide.
API Endpoints
Submit Task & Query Result
# Submit the task
curl --location --request POST "https://api.wavespeed.ai/api/v3/video-effects/romantic-lift" \
--header "Content-Type: application/json" \
--header "Authorization: Bearer ${WAVESPEED_API_KEY}" \
--data-raw '{}'
# Get the result
curl --location --request GET "https://api.wavespeed.ai/api/v3/predictions/${requestId}/result" \
--header "Authorization: Bearer ${WAVESPEED_API_KEY}"
Parameters
Task Submission Parameters
Request Parameters
| Parameter | Type | Required | Default | Range | Description |
|---|---|---|---|---|---|
| image | string | Yes | - | An image to be used as the start frame of the generated video. Requirements: 1. Only accepts 1 image; 2. Only supports dual-person photo; 3. Full-body photo of two subjects with visible feet and thighs for better results; 4. Images can be provided via URLs or Base64 encode; 5. Supported codecs: PNG, JPEG, JPG, WebP; 6. Image aspect ratio must be less than 1:4 or 4:1; 7. Maximum file size: 50MB; 8. Base64 decode length must be under 50MB with appropriate content type string. |
Response Parameters
| Parameter | Type | Description |
|---|---|---|
| code | integer | HTTP status code (e.g., 200 for success) |
| message | string | Status message (e.g., “success”) |
| data.id | string | Unique identifier for the prediction, Task Id |
| data.model | string | Model ID used for the prediction |
| data.outputs | array | Array of URLs to the generated content (empty when status is not completed) |
| data.urls | object | Object containing related API endpoints |
| data.urls.get | string | URL to retrieve the prediction result |
| data.has_nsfw_contents | array | Array of boolean values indicating NSFW detection for each output |
| data.status | string | Status of the task: created, processing, completed, or failed |
| data.created_at | string | ISO timestamp of when the request was created (e.g., “2023-04-01T12:34:56.789Z”) |
| data.error | string | Error message (empty if no error occurred) |
| data.timings | object | Object containing timing details |
| data.timings.inference | integer | Inference time in milliseconds |