1. Preparation
PixVerse Platform Docs
  • Get Started
    • What Is PixVerse AI?
    • Model Capability Map
    • Billing and Usage
    • Quick Start
    • Contact Us
    • Privacy and Data Protection
  • API
    • Preparation
      • Start Here
      • Concurrency Rules
      • Query Task Status
      • Error Codes
      • FAQ
      • Webhook Callbacks
      • Upload Image
        POST
      • Upload Media (Video and Audio)
        POST
      • Verify Uploaded Audio
        POST
      • Get Effect Template List
        GET
      • Get TTS Speaker List
        GET
      • Get Restyle Effect List
        GET
      • Query Task Status
        GET
      • Get Account Balance
        GET
      • Usage Deduction Query
        POST
      • Create Custom Voice
        POST
      • Delete Custom Voice
        DELETE
    • Core Capabilities
      • Text-to-Video
      • Image-to-Video and Video Templates
      • First and Last Frame Video
      • Reference-to-Video (Fusion)
      • Multi-Transition Video
      • Video Extend
      • Image Template Generation
      • Get Image Generation Result
    • Solutions
      • Video Upscale
      • Video Restyle
      • Lipsync
      • Video Edit (Modify)
      • Image Avatar
      • Select Video Mask
      • Sound Effect
      • Subject Replacement (Swap)
      • Motion Control (Mimic)
      • One-click Real Estate Video
      • One-click VibeMV
  • Pricing
    • PixVerse API Pricing
  • Changelog
    • Changelog
  1. Preparation

Concurrency Rules

Concurrency limits control how many generation tasks one account can process at the same time. The applicable quota depends on the account plan and configuration. Check the PixVerse API console for the current account limit.

Concurrency Error#

When the account reaches its concurrency limit, the creation endpoint may return:
CodeMeaningRecommended action
500044Concurrency limit reachedWait for active tasks to reach a terminal state, then retry with exponential backoff and jitter. Reduce client-side parallelism if the error persists.

Recommended Request Pattern#

Maintain a server-side task queue:
Accept request -> Queue task -> Apply account concurrency limit -> Submit to PixVerse -> Poll status or wait for Webhook -> Release local slot
PracticeRecommendation
Request tracingUse a new Ai-trace-id for every submitted request.
Queue managementLimit concurrent submissions on the client side instead of retrying immediately.
Status retrievalPoll Query Task Status at a moderate interval, or use Webhooks.
Retry behaviorUse exponential backoff and jitter for 500044 and temporary service errors.
Terminal statesRelease the local concurrency slot when the task completes or fails.

Long-Running Tasks#

Do not submit duplicate creation requests merely because a task remains in status=5.
Continue querying the original video_id, or wait for its Webhook callback.
Delayed cleanup or refund processing may take time; use the final task state and account ledger as the authoritative record.
Contact PixVerse Support if tasks remain non-terminal for an unusually long period or if the account requires a higher concurrency quota.

Notes#

Avoid repeatedly polling the same video_id at high frequency.
Keep the task queue and retry logic on the server side.
Retain the request Ai-trace-id, video_id, HTTP status, ErrCode, and ErrMsg for troubleshooting.
Previous
Start Here
Next
Query Task Status