Api

API Overview

Base URL, authentication, response envelope, task lifecycle, and HTTP semantics for the Vidrush v1 media API.

Base URL

https://vidrush-ai.com
MethodEndpointAuthenticationPurpose
GET/api/v1/modelsNoModel catalog and pricing; ?type=video (default), image, or music
GET/api/v1/voicesBearer keyText-to-speech voice catalog
POST/api/v1/videosBearer keyCreate a credit-consuming video task
POST/api/v1/imagesBearer keyCreate an image task
POST/api/v1/musicBearer keyCreate a music task
POST/api/v1/speechBearer keyConvert text to speech
POST/api/v1/sound-effectsBearer keyGenerate a sound effect
GET/api/v1/tasks/{taskId}Bearer keyRead task status and result URLs (all media types)
GET/api/v1/creditsBearer keyRead remaining credits

Authenticated requests use Authorization: Bearer sk-.... See Authentication.

Response envelope

Every v1 response is JSON with this envelope:

{
  "code": 0,
  "message": "ok",
  "data": {}
}

Use the HTTP status for transport handling and code for the business result.

HTTP statuscodeMeaning
2000Successful request
400-1Invalid request, model, option, or moderation block
401-1001Missing or invalid API key
402-1002Insufficient credits
404-1Task does not exist or is not accessible to this key
500-1Internal server error

Task lifecycle

Video and image creation are asynchronous — after the create call, poll GET /api/v1/tasks/{taskId} every 5 seconds. Music and audio render synchronously and usually return success with the result URL in the create response; the same taskId still resolves through the task endpoint for a uniform flow.

StatusAction
pendingContinue polling
processingContinue polling
successRead the generated URLs from data.taskUrls
failedStop and report the task failure
canceledStop and report that the task was canceled

Continue with Video, Image, Music, or Audio generation, Tasks, or the model reference.