Choose your video workflow
Pick your input. Build your pipeline.
Make your first request
REST API
Check access and pricing with one request.
- 01Create an API key
Open Settings → API. Store the key on your server.
- 02Choose a mode and send JSON
Follow its request schema and use an idempotency key for paid requests.
- 03Poll, retrieve, publish
Read the job’s status and artifacts, then send the result to your pipeline.
curl https://api.reelsbuilder.ai/api/v1/usage \
-H "Authorization: Bearer $REELSBUILDER_API_KEY"Free account check. Ready to generate? Open the quickstart.
Start with a prompt
Copy the brief into your coding agent.
- 01Copy the integration prompt
Use it in your preferred coding agent.
- 02Add your key on the server
Get an API key and configure your secret store. Keep it out of the prompt.
- 03Verify supported tools
Follow MCP setup or connect your own MCP server to REST.
Integrate ReelsBuilder into this application.
Read the current integration contract:
https://reelsbuilder.ai/docs/api/llms.txt
Discover supported tools and input/output schemas:
https://api.reelsbuilder.ai/api/v1/tools
Use REST at https://api.reelsbuilder.ai/api/v1.
Keep REELSBUILDER_API_KEY in a server-side secret store.
Authenticate with Authorization: Bearer <key>.
Verify access and current pricing with GET /usage.
Choose Stock Video, YouTube Clipping or AI Video from
our requirements. Verify each mode's request schema.
Use a stable idempotency key for paid-request retries.
Poll the returned job until terminal, handle errors,
and retrieve the available video artifacts.
Keep customer branding explicit where supported.
Check account capabilities before private delivery
or other partner features. Report unsupported fields.
Use only tools advertised as executable through MCP
when connecting an agent. Keep credentials off clients.Contract, auth and job handling included. Keep keys out of prompts.
More building blocks
Integration essentials
- Base URL:
https://api.reelsbuilder.ai/api/v1. Send JSON withAuthorization: Bearer <key>. - Async generation: accepted requests return a job handle. Use authenticated polling to retrieve the final artifacts; fields vary by mode.
- Safe retries: keep the same idempotency key when retrying the same paid request. Review error codes and rate limits.
- Billing: every paid call uses your prepaid USD balance. Read
GET /api/v1/usagefor current account prices. - Callbacks: stock, clips, blog, Magic and AI video/influencer accept
webhook_urlfor a signed terminal webhook; polling remains the source of truth.
Customer brands & private delivery
Stock and AI video accept a brand object per request (otherwise the account brand is used), so one account can render for many customers. Send delivery: { visibility: "private" } to keep files off public links (24-hour signed URLs). See the integration guide and the video input map.
Need a hand?
Contact admin@reelsbuilder.ai for partner access or API support. Include the response’s X-Request-Id. Check API health for service status.