Usage Policy

Use BeatSync API for legitimate audio analysis workflows.

BeatSync API is built for developers who need BPM, beat timestamps, and cut-ready timing data for short-form video automation. These rules keep the service predictable for all users.

Audio URL requirements

Submit direct, public HTTPS URLs to audio files, or upload audio with multipart/form-data.
Do not submit private URLs, login-gated URLs, web pages, playlists, or URLs that intentionally hide the file.
Direct file uploads are capped at 50 MB.
Keep files within your plan duration limit: Free 30s, Pro 3min, Ultra 3min, Mega 5min.
You are responsible for having the rights to analyze the submitted audio.

Rate limits and retries

RapidAPI enforces plan quotas and request limits.
Use client-side retries with backoff for transient 503 or 504 responses.
Do not run uncontrolled loops or parallel bursts designed to bypass plan limits.
If you need sustained throughput, contact us before starting production batch jobs.

Refund and billing notes

Consumed requests are generally non-refundable.
Requests may still count when the submitted URL or uploaded file is invalid, inaccessible, unsupported, too large, or over the plan duration limit.
If BeatSync API is unavailable and a request was not processed, contact us with the RapidAPI request ID, timestamp, plan, and response body.
RapidAPI subscription billing, upgrades, downgrades, and cancellations are managed through RapidAPI.

Prohibited use

Do not use the API to analyze audio you are not authorized to process.
Do not submit malware, abusive traffic, or URLs intended to attack third-party systems.
Do not resell raw API access as a pass-through service without written permission.