Skip to main content

​
Overview

The BeatPass API supports authentication for approved developer integrations.
API access is invite-only. Developer tokens are granted on a case-by-case basis. To request access, contact contact@beatpass.ca. See Authentication for details.

​
Authentication Method

All authenticated API requests use Bearer tokens in the Authorization header: 
GET /api/v1/tracks
Authorization: Bearer {your-token}
Accept: application/json

Bearer Tokens

Personal access tokens for approved developer integrations

Token Expiration

Tokens expire after 90 days and must be regenerated

​
Authentication Errors

Token missing, invalid, or expired.Solution: Verify your token is correct and has not expired. Contact support if you need a new token.
{ "message": "Unauthenticated." }
Your account lacks permission for this resource.Solution: Ensure your account has been granted API access. Contact support if you believe this is an error.

​
API Access Tiers

The BeatPass API uses a two-tier access model for external consumers:
TierAuth MethodData LevelUse Case
PublicNoneMinimal (id, name, model_type only)Basic resource identification
TokenAuthorization: Bearer {token}Rich (pricing, plays, BPM, licensing)Approved developer integrations
Unauthenticated API requests return minimal data by design. To receive rich responses with pricing, play counts, licensing info, and more, you must authenticate with a Bearer token. This protects the platform catalog from scraping.

​
What Each Tier Returns

Track: id, name, image, created_at, model_type, duration_textArtist: id, name, model_typeGenre: id, name, display_name, model_typeAlbum: id, name, model_type, image, release_dateNo pricing, play counts, BPM, key/scale, licensing, or internal fields.

​
Requesting API Access

API access is granted on a case-by-case basis to approved developers and partners.
1

Contact BeatPass

Email contact@beatpass.ca with your use case, expected request volume, and organization details.
2

Review & Approval

The BeatPass team will review your request. Approved developers will receive API access on their account.
3

Generate Token

Once approved, navigate to Account Settings → Developers and click Create to generate your token. Copy it immediately — it is only shown once.
4

Authenticate Requests

Include the token in the Authorization header of all API requests:
Authorization: Bearer {your-token}

​
Token Details

PropertyValue
AccessInvite-only, granted by BeatPass team
Expiration90 days from creation
Header formatAuthorization: Bearer {token}
Treat your API token like a password. Do not share it, commit it to version control, or expose it in client-side code. Misuse of API tokens will result in immediate revocation and potential account termination.

​
Revoking Tokens

To revoke a token, return to Account Settings → Developers and click Delete next to the token.

​
Security

All API requests must use HTTPS. Non-secure requests are rejected.
Never expose tokens in client-side code, URLs, or public repositories.
All API activity is logged and monitored. Abusive patterns (scraping, excessive requests, unauthorized access attempts) result in immediate token revocation and account termination.

​
Next Steps

API Reference

See available endpoints.

Rate Limits

Understand request limits.
Last modified on February 10, 2026