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 upload requirements

Submit audio with multipart/form-data using a form field named file.
Basic and Pro both allow up to 10 MiB and 120 seconds of audio.
Both plans use a Hard Limit with no overage.
You are responsible for having all rights and permissions required 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

4xx user errors include invalid or unsupported files, size or duration violations, authentication failures, rate limits, and exhausted quota. These requests may count under RapidAPI's rules.
5xx service errors, including 503 and 504, may qualify for a credit or refund after manual review.
Contact support with both the request ID and task ID, timestamp, plan, and response code. Support verifies the failure and handles any credit or refund manually through the available marketplace process.
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 recordings involving children, medical or health information, identity verification, biometrics, or other regulated sensitive uses.
Do not submit malware, abusive traffic, or files intended to attack processing systems.
Do not resell raw API access as a pass-through service without written permission.