Video Face Swap API

Transfer a source face into a video. Compare the dedicated face-swap endpoint with motion-transfer workflows only where their input/output behavior matches.

Muapi Video Face Swap API landing page · API reference · Playground · Create an API key

Related Projects

• Image-Face-Swap-API
• AI-Avatar-Lipsync-API

What this API covers

Use the endpoint that matches the task and input media. The routes below are enabled Muapi model IDs checked against the current model catalog; availability, request fields, and pricing can change, so verify the linked landing page and endpoint schema before production use.

Endpoint	Purpose	Category
ai-video-face-swap	Video Faceswap	Video to Video

Quick start

Muapi uses an asynchronous REST contract. Submit a JSON request with your API key, save the returned request_id, then poll the result endpoint. Replace sample URLs with files you control and fields with values supported by the selected endpoint.

curl -X POST https://api.muapi.ai/api/v1/ai-video-face-swap \
  -H "Content-Type: application/json" \
  -H "x-api-key: $MUAPI_API_KEY" \
  -d '{
    "image_url": "https://example.com/replace-with-your-file",
    "video_url": "https://example.com/replace-with-your-file"
  }'

Request fields in this example

Field	Requirement	Notes
image_url	Required	Swap URL of the input image.
video_url	Required	Target URL of the input video. Resolution must be less than 1280x720 or 720x1280. Size must be less than 10mb. Video frame cannot be greater than 600

Poll for the result

curl "https://api.muapi.ai/api/v1/predictions/$REQUEST_ID/result" \
  -H "x-api-key: $MUAPI_API_KEY"

Poll until the task status is completed or failed. Read the response’s output URLs on completion; download outputs you need to retain, since provider-hosted URLs may expire.

Choosing an endpoint

Compare supported inputs and output behavior first, then resolution, duration, quality controls, latency, and price for your use case. Similar names do not guarantee interchangeable request schemas. This repository lists representative routes; the canonical landing page contains the current task-specific explanation, examples, and pricing context.

Errors and production notes

• Keep the API key in an environment variable; do not commit credentials.
• Validate inputs against the selected endpoint’s current schema.
• Handle non-success HTTP responses and failed task states explicitly.
• Retry only when appropriate for the error; avoid submitting duplicate billable jobs after a timeout without checking the original request_id.
• Confirm current pricing and availability on the Muapi page before estimating production cost.