Skip to main content

Overview

This catalog documents common errors you may encounter across BeatPass API endpoints, along with their meanings and suggested resolutions.

Error Response Format

All errors follow this structure:

HTTP Status Codes

400

Bad Request Malformed syntax

401

Unauthorized Auth required

403

Forbidden Not permitted

404

Not Found Doesn’t exist

409

Conflict State conflict

422

Unprocessable Validation failed

429

Too Many Rate limited

500

Server Error Internal issue

Authentication Errors

Invalid credentials

401 Wrong email or password combination.Resolution: Verify your credentials. Use “Forgot Password” if needed.
403 Account has been suspended.Resolution: Contact contact@beatpass.ca for assistance.
403 Email verification is pending.Resolution: Check your inbox for the verification link. Request a new one if needed.
401 Your authentication token has expired.Resolution: Generate a new token from Account Settings → Developers.
401 No valid authentication token found.Resolution: Include a valid Bearer token in your request. Contact support if your token has expired.

Track & Upload Errors

422 File exceeds maximum size (256 MB).Resolution: Compress or reduce file size before uploading.
422 Unsupported audio format.Resolution: Use WAV, FLAC, or AIFF. MP3 files are not accepted.
422 Track duration must be at least 1 second.Resolution: Ensure the uploaded file has a valid duration.
422 Title, BPM, or Genre not provided.Resolution: Fill in all required metadata fields.

Purchase & Licensing Errors

Purchase Flow

Payment Errors

License Errors


Beat Request Errors

Creation

Submission

Deletion & Renewal


Producer Program Request Errors

These errors apply to Backstage request creation and submission eligibility checks.
Backstage create submissions are blocked globally per user when a pending or revoked request exists, regardless of request type (become-artist, verify-artist, or claim-artist). If both statuses exist, pending takes precedence.

Audio Recon Errors

Audio Recon matches are only available for tracks with a verified artist profile. If the track’s primary artist is not verified, the response will return an empty matches array with artist_verified: false.

Messaging Errors

Sending Messages

Conversation


Collection & Library Errors

Saves & Playlists

Collaborative Playlists


Social & Following Errors

Following

Reposts


Radio Errors


Rate Limiting

Rate Limit Response

Rate Limit Headers

Handling Rate Limits

Exponential Backoff

Wait, then double the delay on each retry attempt.

Check Headers

Monitor X-RateLimit-Remaining before making requests.

Queue Requests

Space out API calls to stay under limits.

Cache Responses

Reduce redundant calls by caching data locally.

Server Errors (5xx)

500 - Internal Server Error

500 An unexpected server-side issue occurred.Resolution: Retry the request. If persistent, contact support with the timestamp and endpoint.
503 Platform is undergoing maintenance.Resolution: Check the status page for updates.
504 Request took too long to process.Resolution: Retry with a smaller payload or try again later.
Server errors (5xx) are logged automatically. If you encounter persistent issues, contact support with the approximate time and endpoint details.

Troubleshooting Checklist

1

Check Error Message

Read the message field for human-readable explanation.
2

Check Validation Errors

Review errors object for field-specific issues.
3

Verify Authentication

Ensure your Bearer token is valid and included in the Authorization header.
4

Check Rate Limits

Review X-RateLimit-* headers.
5

Retry with Backoff

For transient errors, wait and retry.
6

Contact Support

For persistent issues, provide error details and timestamps.

API Overview

API fundamentals.

Rate Limits

Throttling details.
Last modified on February 26, 2026