API Usage Policy

Purpose and scope

This Policy governs access to and use of (1) Radiocast database APIs — programmatic interfaces that read or write Radiocast platform data over HTTPS for the Service at https://radiocast.net (including official client SDK patterns, authenticated backend routes, databases, realtime channels, serverless endpoints, and similar mechanisms); and (2) Radiocast Panel APIs — the HTTP API at https://panel.radiocast.net/api for AzuraCast panel operations hosting on Radiocast, described by the Panel OpenAPI specification.

Use of APIs is incorporated into our Terms of Service by reference. Defined terms such as “Service”, “User”, and “User Content” have the meanings given in the Terms unless this Policy expressly states otherwise. If anything conflicts between this Policy and the Terms, the Terms govern unless expressly stated herein.

Deemed acceptance. You are considered to have accepted this Policy and all applicable API terms as soon as you obtain API credentials, configure integrations that call our endpoints, or otherwise use the APIs (including any request to Radiocast-managed database, application, or Panel API URLs), whether or not you have read this page in full. Continued use after we post updates constitutes acceptance of the revised Policy to the extent permitted by law.

Authorization and separation of API families

Database APIs and Panel APIs may differ in hostname, credentials, quotas, scopes, billing, and availability. A right granted for one category does not automatically grant rights to the other. You may only call endpoints your account role, subscription, and Radiocast configuration permit.

Credentials and security

You are responsible for activity performed with credentials issued to you (API keys, tokens, webhook secrets, session identifiers, Panel API keys, or similar). Maintain least-privilege credentials, revoke and rotate compromised keys promptly, and do not hardcode long-lived privileged secrets in public clients, embeds, or source repositories. Do not use another person's credentials or attempt to access data or actions outside your permitted scope.

Access, revocation, and circumvention

Radiocast may restrict, suspend, or permanently revoke your access to any or all APIs, keys, quotas, webhooks, realtime channels, or related programmatic interfaces— at any time and without owing you a continuing right to maintain that access—with or without prior notice except where applicable law requires otherwise. Reasons may include policy violations, billing issues, operational or security incidents, sunsets of features, changes to offerings, or no reason stated.

You must not attempt to bypass, circumvent, undo, or replace revoked, suspended, throttled, or blocked API access—for example through alternate accounts without authorization, shared compromised credentials, IP or header evasion, proxying across blocked paths, exploiting undocumented endpoints to recover functionality, or similar means. Unauthorized continued or evasive usage may be treated as a violation of this Policy and the Terms.

Acceptable use

You may use Radiocast APIs only in compliance with applicable law, our Terms, our Station Guidelines, and applicable copyright or licensing obligations (including for streamed content).

Limits, quotas, and changes

Radiocast may impose or adjust rate limits, concurrency caps, payload limits, feature flags, deprecations, and availability for any API tier. Clients should use retries with backoff and avoid unnecessary polling or redundant writes. Except where expressly committed in a separate enterprise agreement, APIs are provided AS IS without a separate uptime SLA.

Third-party software

The Radiocast panel runs on AzuraCast, an independent third-party open-source radio management platform. References to Panel APIs describe technical compatibility with that software's published API—they do not imply any affiliation, endorsement, partnership, or joint venture between Radiocast and the AzuraCast project or its contributors. Separate license obligations (including AGPL, where applicable) may apply to AzuraCast and are independent of Radiocast's hosting terms for your account. You remain responsible for your own compliance when you invoke, modify, or redistribute third-party software.

Enforcement

Radiocast may log API traffic for operations, billing, fraud prevention, and security. Suspension or termination of credentials, accounts, integrations, or the Service may occur for violations of this Policy or the Terms, or when necessary to protect others or comply with law. See the Terms for dispute terms, disclaimers of warranties, limitations of liability, and indemnification.

If your use of the APIs violates this Policy or the Terms, or if you circumvent or disregard restrictions on access, Radiocast reserves the right to invoice you for resulting costs and remedial charges—including, without limitation, charges relating to excess load, remediation, circumvention, continued use after access has been revoked or restricted, platform abuse, or unauthorized access—at an amount Radiocast deems fair and reasonable under the circumstances, in addition to any other remedies Radiocast may have.

Intellectual property and DMCA

API access does not grant extra IP rights beyond the Terms. Repeat: you must have applicable rights for content you ingest, upload, broadcast, or process via APIs. Report copyright matters as described in our Terms; contact contact@radiocast.net.

Contact

Questions about this Policy may be sent to contact@radiocast.net.