> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# Using BeatAPI in Make

> Start with a shareable BeatAPI music-video template or create an HTTP scenario for another capability.

# Using BeatAPI in Make

The [shareable music-video template](https://www.make.com/en/integration/19483-create-ai-music-videos-from-a-prompt-with-openai-kie-and-beatapi?templatePublicId=19483) combines **OpenAI, Kie, and BeatAPI**. It plans a concept, generates source audio and an image, then asks BeatAPI to render the video. It is a multi-service template, not a native BeatAPI Make app or proof that every BeatAPI capability is available as a Make module.

## Use the template

1. Open the template and create a scenario from it.
2. Add the required OpenAI, Kie, and BeatAPI credentials in Make; never paste credentials into an exported blueprint.
3. Review the input fields and the API calls before the first run. The workflow can consume credits at each service.
4. Run once with your own authorized assets and inspect every task ID, status branch, and final output.

For another BeatAPI capability, use Make's HTTP module with `Authorization: Bearer <your BeatAPI key>`. Search the current capability catalogue, inspect the exact reference and price, and follow its returned execution strategy. Some models use a direct API; asynchronous media tasks need status polling. A local general-purpose Search/Inspect/Run blueprint exists, but it has not completed a Make import and runtime check and is not published as a template.

On September 26, 2026, the music-video template was shareable with a **Create new scenario from template** action; its Make team dashboard showed **Pending approval**. An approved, indexed Make Marketplace listing remains a separate state.