VidGuy Docs

Build videos faster with VidGuy

Guides and best practices for turning prompts into platform-ready videos.

Errors

Snacks API errors use a shared JSON shape:

{
  "error": "Invalid request",
  "message": "Optional human-readable guidance",
  "details": {}
}

details is populated when the request fails Zod validation; keys match the request fields (e.g. details.fieldErrors.brandId).

Status	Meaning
`400`	Invalid body, query, or path input
`401`	Missing, invalid, or revoked API key
`402`	Insufficient credits, or payment required for x402 top-up
`403`	Authenticated but not allowed
`404`	Brand or snack not found (or not owned by your API key)
`429`	Rate limit or concurrency quota exceeded
`500`	Internal server error
`502`	Failed to dispatch the snack worker (credits refunded — retry safe)
`503`	Snack pipeline temporarily unavailable

Retry 429, 502, and 503 with exponential backoff (start at 2s, cap around 30s).
Do not blindly retry 400, 401, 403, or 404 — fix the request first.
For async snack jobs, poll the job at GET /api/v1/jobs/{id} instead of resubmitting POST /api/v1/snacks (resubmitting double-charges credits).