Skip to content

Radiorecord API

This API provides a JavaScript library for interacting with radiorecord.ru, allowing users to access charts, tracks, and other resources related to music streaming. It simplifies the integration of radiorecord functionalities into applications, making it easier for developers to use its features.

Open documentation ↗
AuthHTTPSNo CORSMusic

Verified today: 100% uptime

API key

Unconfirmed

HTTPS

Supported

Browser calls

No, needs a proxy

Status

Live · 98/100

Overview & Architectural Role

Radiorecord API provides programmatic access to this api provides a javascript library for interacting with radiorecord.ru, allowing users to access charts, tracks, and other resources related to music streaming. it simplifies the integration of radiorecord functionalities into applications, making it easier for developers to use its features. Delivered over secure HTTPS protocols, it exposes structured endpoints designed to integrate cleanly into modern frontend frameworks, backend microservices, and automated data pipelines without requiring local database provisioning.

Who it is built for

Engineers building web dashboards, mobile applications, CLI utilities, or background cron workers in need of reliable music data feeds.

Architectural Advantage

Consuming Radiorecord API removes the operational overhead of running custom scrapers, orchestrating headless browser fleets, or manually seeding and maintaining a local database. Instead of reverse-engineering volatile DOM layouts or dealing with anti-bot IP blocks, your application connects directly to a standardized JSON interface designed for backend ingestion with consistent schema schemas. Dedicated authentication ensures rate quotas and credential tracking per project environment.

What our checks found

Health score
98/100
Reliability
100%
Average latency
2740ms

Last checked 2026-10-24. Measured independently, not self-reported by the provider.

Core Use Cases & Architecture Ideas

Practical real-world patterns for integrating Radiorecord API into software systems.

Automated SaaS Feature Integration

Embed data and functionality from Radiorecord API directly into application onboarding, profile enrichment, or reporting dashboards.

Architecture: Backend service worker fetches Radiorecord API during user workflows, caches responses in Redis, and hydrates UI state.

Scheduled Reporting & Monitoring Bot

Periodically extract updates from Radiorecord API to generate daily digests, analytics reports, or Slack notifications.

Architecture: A scheduled GitHub Action or cron worker executes a lightweight script calling Radiorecord API, formatting markdown summaries for stakeholders.

Rapid Prototyping & Hackathon Showcase

Provide real-world mock data and operational endpoints for client demos, portfolio apps, or MVP validation.

Architecture: Static client SPA queries Radiorecord API directly to populate mock dashboards, graphs, and interactive UI states without a custom backend.

Code Implementation Examples

Production-ready starting templates with error handling for Radiorecord API.

// Authentication requirement is unconfirmed. Check the documentation before relying on this.
// Modern native fetch with error handling
async function callApi() {
  try {
    const response = await fetch('https://github.com/api/v1/resource', {
      method: 'GET',
    headers: {
      'Authorization': 'Bearer YOUR_TOKEN',
      Accept: 'application/json',
    },
    });

    if (!response.ok) {
      throw new Error(`HTTP ${response.status}: ${response.statusText}`);
    }

    const data = await response.json();
    console.log('Response payload:', data);
    return data;
  } catch (error) {
    console.error('API request failed:', error);
    throw error;
  }
}

// callApi();

This API does not send CORS headers, so a browser will block a direct call from your front end. Call it from your server, or put a small proxy in front of it.

Response Payload & Live Testing

Inspect the expected JSON structure returned by Radiorecord API.

Expected JSON Response Payload

Authentic sample payload structure to evaluate schema attributes before integration.

{
  "status": 200,
  "api": "Radiorecord API",
  "endpoint": "/radiorecord-api",
  "data": {
    "id": 101,
    "title": "Radiorecord API Sample Payload",
    "description": "This API provides a JavaScript library for interacting with radiorecord.ru, allowing users to access charts, tracks, and other resources related to music streaming. It simplifies the integration of radiorecord functionalities into applications, making it easier for developers to use its features.",
    "verified": true,
    "category": "Music",
    "updated_at": "2026-10-24T07:39:50.583Z"
  },
  "meta": {
    "response_time_ms": 2740,
    "cached": false
  }
}
Format: application/json

Integration Considerations & Best Practices

Technical factors to keep in mind when integrating Radiorecord API into production environments.

Implement In-Memory or Edge Caching

Avoid triggering rate limits on public feeds by caching response payloads in Redis, Vercel KV, or standard HTTP Cache-Control headers with a 5-to-15 minute TTL.

Zero-Credential Environment Protection

While no API key is required, public keyless pools often share global rate limits. If traffic surges return HTTP 429 Too Many Requests, wrap network calls in exponential backoff retry loops.

CORS Proxy Required for Browser Frontend Calls

This API does not send Access-Control-Allow-Origin response headers. Direct fetch() calls from browser JavaScript will fail due to Same-Origin Policy. Route your calls through a server backend or lightweight edge proxy.

Validate HTTP Status Before Parsing JSON

Always inspect response.ok before executing response.json(). Upstream services returning 4xx or 502 Bad Gateway often serve HTML error pages, which cause syntax errors when parsed as JSON.

Where this listing comes from

Aggregated from one public source (freepublicapis), then normalised and checked by us.

Report an issue with this listing ↗

Other Music APIs

See all 45 →

Openwhyd

Music

Openwhyd is a free and open-source music curation service that allows users to create playlists of music tracks from various streaming platforms (YouTube, SoundCloud, Vimeo, Deezer…) and to discover the music posted by other users.

No keyCORSHTTPS

Verified today: 100% uptime

View Details

Gaana

Music

API to retrieve song information from Gaana

No keyHTTPS

Verified today: 100% uptime

View Details

JioSaavn

Music

API to retrieve song information, album meta data and many more from JioSaavn

No keyHTTPS

Verified today: 100% uptime

View Details

SearchLy

Music

Similarities search based on song lyrics

No keyHTTPS

Verified today: 100% uptime

View Details

Radiorecord API — common questions

Answered from what our own scheduled checks found, not from the provider's marketing.

Is Radiorecord API free to use?

Radiorecord API is listed in our free catalogue, but it requires some form of authentication, so you will need to register before your first call. Providers frequently reserve higher limits and commercial use for paid plans.

Does Radiorecord API need an API key?

Radiorecord API requires some form of authentication. Check the provider's documentation for which scheme it expects.

Can I call Radiorecord API from browser JavaScript?

Not directly. Radiorecord API did not return CORS headers when we checked, so the browser will block your page from reading the response even though the request itself succeeds. Call it from a server, or put a small proxy in front of it.

Is Radiorecord API still working?

Yes, as of 2026-10-24. Our automated check reached Radiorecord API and recorded a 100% reliability score with a median response time of 2740 ms. We re-check on a schedule, and this page updates with the result.

Is Radiorecord API available over HTTPS?

Yes. Radiorecord API serves over HTTPS, so you can call it from a secure page without triggering a mixed-content block.