Additional terms for the public API

These API Terms supplement the general Terms of Use of Boocord Music. They are based on the regular Terms dated 21.06.2026. This page only covers the public API without login under /api/request/ and the API documentation under /api/.

This English version is provided for convenience. The German version is the legally binding version. If there are any differences between the German and English versions, the German version prevails.

API docs General terms Deutsch

1. Scope

These additional terms apply to all access to documented public API endpoints, whether access happens through a website, app, bot, overlay, or another tool.

  1. The fact that no login is required does not mean the API is rule-free or unlimited.
  2. Protected or undocumented endpoints are not part of this public permission.
  3. If rules conflict, the stricter rule applies to API usage.

2. Permitted use

Fair use of the Public API is allowed for integrations, interfaces, players, directories, dashboards, and creative projects.

  1. You may display and process metadata, covers, profile information, feed data, and public playlists, albums, and artists.
  2. You may use song and image paths in a user interface for display or playback.
  3. External use of songs in videos, streams, products, or other projects is governed by the license shown for the respective song. These API Terms only regulate use of the API itself.

3. Not permitted

Anything that unreasonably burdens the service technically, economically, or legally, or reuses the content as a separate raw dataset, is not allowed.

  1. No bulk mirroring, no mass download of the catalog, and no replacement service based on the API.
  2. No resale, sublicensing, or separate distribution of audio, image, or metadata as your own data service.
  3. You may not bypass protections such as login, roles, visibility, rate limits, or cache protection.
  4. No security scans, load tests, brute-force attempts, or intentionally faulty automated requests without explicit consent.
  5. No use for unlawful, misleading, or rights-infringing purposes.

4. Fair use, caching, and polling

The Public API is intended for normal product usage, not aggressive continuous polling.

  1. You must respect 429 responses and the Retry-After header.
  2. Where technically reasonable, cache responses briefly instead of repeatedly requesting the same endpoint.
  3. image.php may not be used as a general external image proxy. It is only intended for local files below files/.
  4. Sub-second polling for normal UI updates is not allowed.

5. Content and presentation

The API returns content from Boocord Music. You may not hide its origin or present the content without clear context as your own offering.

  1. If your integration visibly shows Boocord content, users must be able to recognize its source. A source label such as "Boocord Music" is the expected standard.
  2. Covers, profile images, and other media may not be altered or embedded in a misleading or distorting way.
  3. Audio files may not be offered as a separate download archive or raw dataset.

6. Availability and changes

As stated in the general Terms of Use, there is no entitlement to permanently uninterrupted availability. This also applies to the API.

  1. Endpoints, fields, limits, response structures, and content may be changed or removed at any time.
  2. There is no SLA, no guaranteed backward compatibility, and no entitlement to unlimited use.
  3. Experimental or user-dependent fields may be adjusted without prior notice.

7. Privacy and public data

The Public API is intended for public data. Privacy, personality rights, and the general Boocord rules still apply.

  1. Public profiles and feed data may not be misused for spam, profiling, doxxing, or unwanted contact.
  2. If you store API data, you are responsible for complying with all applicable privacy laws.
  3. Additional data visible only in your own login context is not automatically approved for disclosure to third parties.

8. Enforcement

Boocord may take technical or organizational measures in case of abuse or risks to stability, security, or third-party rights.

  1. This may include rate limits, temporary blocks, permanent blocks, or disabling individual endpoints.
  2. There is no entitlement to unblocking, prior notice, or continued operation of a specific public permission.
  3. Further statutory or contractual rights of Boocord remain unaffected.

Short version

Allowed: normal integrations, players, directories, dashboards, and creative projects. Not allowed: aggressive load, bypassing protections, bulk rehosting, and reuse of the data as a separate raw data or download service.