Interactive reference for the VidGuy Snacks API — endpoints to register brands, generate short-form video concepts, poll jobs, and manage credits. Also includes endpoints for publishing to hosted, done-for-you social accounts. Use the interactive reference below to explore endpoints, request schemas, and example responses. The API powers programmatic short-form video generation: register a brand, submit a creative brief, poll the resulting job, fetch the rendered video, and manage your credit balance — all from your own backend, agent, or workflow tool.
Authenticate with an API key, then submit a structured brief describing the video you want: niche, hook, voice style, music mood, target platform, and optional brand kit. VidGuy handles script generation, voiceover synthesis, stock and AI visual assembly, captioning, and final export. Jobs are asynchronous — submit, poll status, and download the finished MP4 or share-ready URL when complete. Use the credits endpoint to read your remaining balance, and use the brand endpoints to keep visual identity consistent across every render.
Most integrations follow the same pattern: register a brand once with logo, colors, and voice; create video jobs from prompts or RSS items; poll until the job reports completion; then fetch the result and post it to your social platforms. Recommended polling cadence is every 5 to 10 seconds with exponential backoff on errors. Rate limits and credit usage are documented in the guides linked below.
Beyond your own connected social profiles, VidGuy can run done-for-you hosted accounts on your behalf. The API lets you list your hosted accounts and their status, publish a finished video or photo post immediately — anything beyond an account's daily pace is queued and published automatically — track each post's views, likes, and comments, edit an account's profile, and remove a post while it is still scheduled. It is the same render-then-publish flow as connected accounts, with VidGuy handling the account operations.
Looking for a guided walkthrough instead of the raw OpenAPI spec? Start with the documentation below: