Tangle API terms

Version 2026-10-08. These terms apply on top of the Tangle Terms of Service.

People own their collections

A collection belongs to the person who built it. You may read and change it only to do what that person asked your app or agent to do, and only with the scopes they granted. Don’t ask for scopes you don’t use.

What you may do with the data

• Keep only what your app needs, and delete it when the person disconnects your app or asks you to.
• Don’t sell collection data, share it with third parties, or use it to profile people or train models without their explicit consent.
• Don’t combine one person’s data with another’s unless both of them asked for it.
• Respect the music platforms’ own terms for the links and ids Tangle gives you.

Keep tokens safe

• Treat tokens and client secrets as passwords: never put them in public code, URLs or logs.
• Verify webhook signatures, and use HTTPS everywhere.
• Tell Tangle at once at [email protected] if you think a token or secret leaked.

Fair use

• Stay within the rate limits, and don’t try to get around them with more tokens or accounts.
• Use only the public endpoints under /v1 and /oauth.
• Don’t present your app as made or endorsed by Tangle.

Changes and access

The API is in beta. Tangle may change it, rate-limit it, or revoke tokens and apps that break these terms or put people’s collections at risk. Within /v1 we only add fields; breaking changes come in a new version with notice.