Quick Links
Quickstart
Get up and running quickly
Authentication
Learn the auth flow
API Reference
Explore all endpoints
Integration Requests
If you’re interested in integrating with BeatPass (partnerships, data licensing, embedded players), contact support to discuss options.Partnership Inquiries
Contact support for integration discussions.
Base URL
All API requests use the base URL:API Surface
The BeatPass API provides comprehensive functionality across the platform:- Content & Discovery
- Commerce & Licensing
- Producer Tools
Tracks
List, view, upload, update, delete tracks
Albums
Album management and metadata
Artists
Artist profiles, followers, tracks
Playlists
Create, manage, share playlists
Search
Full-text search across content types
Genres
Genre listing and filtering
Lyrics
Synced and plain lyrics management
Radio
Personalized music recommendations
Request Format
HTTP Methods
GET
Retrieve data
POST
Create resources
PUT
Update resources
DELETE
Remove resources
Required Headers
Authenticated requests must include a valid Bearer token. See the Authentication guide for details.
Response Format
Success Response
Responses vary by endpoint. Most return data directly:Error Response
Pagination
Paginated endpoints use standard :Authentication & Data Access
The BeatPass API uses a for external consumers:| Tier | Auth | Data |
|---|---|---|
| Public | None | Minimal (id, name, model_type only) |
| Token | Bearer {token} | Rich (pricing, plays, BPM, licensing) |
Endpoint Categories
The API provides read access to public content (tracks, artists, albums, genres, search) and authenticated access to user-specific features (library, playlists, messaging, purchases, analytics). See the API Reference for the full endpoint listing.Rate Limiting
The API enforces rate limits to ensure fair usage and platform stability. Exceeding limits returns a429 Too Many Requests response.
Rate Limits Reference
View rate limiting documentation and best practices.