Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vmeg.ai/llms.txt

Use this file to discover all available pages before exploring further.

The Open API uses the JSON code field for business outcomes. HTTP status handles transport (for example 401 for auth failures), but success and failure semantics are defined by code.

​
Code reference

codeNameDescription
200SuccessRequest succeeded
400Bad RequestInvalid or failed validation
401UnauthorizedAPI Key missing or invalid
402Payment RequiredInsufficient credits or quota
404Not FoundResource not found
409ConflictIdempotency key already used
413Payload Too LargeUpload or body exceeds limit
422Unprocessable EntityValid format but cannot be processed
500Internal Server ErrorServer error
502Bad GatewayUpstream processing failure

​
Response shape

{
  "code": 402,
  "message": "Insufficient quota",
  "data": null
}
  • Success: code === 200, payload in data
  • Failure: human-readable message for logs and support

​
Common cases

Returned when the same X-Idempotency-Key is reused on a mutating POST endpoint within the idempotency TTL. The response may include Retry-After: 2. See Idempotency.
Returned when a task cannot deduct project credits (TTS, translation, voice clone, media translation). See Pricing or add credits on vmeg.ai.
An upstream service failed or timed out. Poll GET /openapi/v1/tasks/detail with the taskId (your task list on vmeg.ai does not include Open API jobs). If a webhook is configured, wait for retries.